Skip to main content
Glama

Search service providers

naut_search_services
Read-only

Search and filter service providers. Costs 5 credits.

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": "naut_search_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoText to match against names, handles and domains.
pageNoPage number, from 1.
sortNo
limitNoRows per page, 1 to 100. Default 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known. The description does add one piece of genuinely useful context not present in structured fields — the 5-credit cost — but it says nothing about result shape, pagination behavior, or what an empty result looks like for a paged search.

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

Conciseness5/5

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

Two short sentences, purpose first and the credit cost second. No filler or redundancy; every phrase carries information.

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

Completeness3/5

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

For a four-parameter, no-required-args search with no output schema, the definition covers the essentials of what it searches and what it costs. It leaves gaps around result contents, paging behavior and sorting semantics that an agent would want before calling it repeatedly.

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

Parameters3/5

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

Schema description coverage is 75%, with q, page and limit documented in the schema and sort carrying an enum of name/recent. The description adds no meaning beyond the schema — it doesn't explain matching semantics for q or the tradeoff between the sort modes — so the baseline 3 applies.

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?

"Search and filter service providers" names a specific verb (search/filter) and a specific resource (service providers), which is enough to distinguish it from the getter sibling naut_get_service and from the other search_* tools by resource. It stops short of explicitly contrasting itself with those siblings, so a 4 rather than a 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 tool versus naut_get_service (known provider) or the other naut_search_* variants, and no stated prerequisites. Usage must be inferred entirely from the tool name and the word "service providers".

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