Skip to content

Definition

Grouping related tools under common prefixes or suffixes so agents can disambiguate tools and services when many tools are in context.

Key points

  • Agents may face hundreds of tools across multiple MCP servers; namespacing clarifies tool boundaries.
  • Group related tools under common prefixes/suffixes:
    • By service: asana_search, jira_search.
    • By resource: asana_projects_search, asana_users_search.
  • Choice of prefix- vs suffix-based namespacing has non-trivial effects on tool-use evaluations — worth testing.
  • Names that reflect natural subdivisions of tasks simultaneously reduce the number of tools and tool descriptions loaded into context.

Why it matters for the exam

  • Namespacing is the recommended answer when many tools/servers cause selection ambiguity or context bloat.
  • Distinguishes service-based vs resource-based grouping conventions.

Common gotchas

  • Prefix vs suffix is not cosmetic — it measurably shifts eval results, so it must be tested rather than assumed.
  • Namespacing is about disambiguation and context economy, not just aesthetics.

See also

Sources