Skip to main content
Glama

GTM Daily

Search GTM agencies

search_gtm_agencies
Read-onlyIdempotent

Search published GTM Engineering agencies and consultants. Sponsored placements are never mixed into this ordering.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_gtm_agencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
toolNoA tool in the agency's stack
limitNoMax results (default 10, max 50).
queryNo
cursorNoOpaque cursor from a previous result's next_cursor.
regionNo
serviceNo
categoryNoCategory slug from get_gtm_marketplace_categories
delivery_modelNo

Output Schema

NameRequiredDescriptionDefault
okNo
codeNo
dataNo
statusYes
messageNo
warningsNo
next_stepNo
next_cursorNo
action_grantNo
approval_urlNo
correlation_idYes
missing_fieldsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety is covered. The description adds two useful behavioral facts: results are limited to published listings, and sponsored placements never influence ordering — a meaningful disclosure about result composition. It says nothing about pagination behavior or result volume, which would have raised the score.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the purpose, with no filler. The second sentence earns its place by disclosing ranking integrity, though it occupies the slot where filter guidance would have been more useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return shape needn't be described. But for a 9-parameter faceted search with 44% schema coverage, the description leaves the agent guessing about sort semantics, filter value vocabularies, and how this search relates to the single-record get_gtm_agency sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 44% across 9 parameters, so the description is expected to compensate — and it adds nothing. Unexplained semantics remain: what 'picks', 'saved', 'reviewed' mean for sort, what values region/service/delivery_model accept, and what 'published' implies for filtering.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Search published GTM Engineering agencies and consultants.' That is clearly distinct from get_gtm_agency (single record) and search_gtm_tools (tools, not agencies). It doesn't explicitly name a sibling to contrast with, so it stops short of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this vs. get_gtm_agency, search_gtm_tools, or compare_gtm_tools, and no advice on which of the 9 optional filters to combine. The only contextual sentence concerns sponsored placements, which is a ranking property, not a usage rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources