Skip to main content
Glama

Get a service provider

naut_get_service
Read-only

One service provider with its team. Costs 5 credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "naut_get_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesService provider slug or id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds two genuine behavioral facts beyond that: the payload includes the provider's team, and the call consumes 5 credits. It omits what happens on an invalid slug (error vs empty, whether credits are still charged), which matters for a metered read.

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 sentences, front-loaded with what is returned, with cost immediately after and zero filler. The phrasing "One service provider with its team" is slightly clipped but not ambiguous.

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 one-parameter read with full schema coverage and annotations covering the safety profile, this is close to sufficient. The remaining gap is failure behavior for an unknown slug combined with the stated credit cost — an agent cannot tell whether a miss still burns credits.

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 coverage is 100%, and the schema itself documents the single parameter as "Service provider slug or id." The description adds nothing about slug format or where to obtain it, so the baseline of 3 applies since the schema carries the full burden.

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?

"One service provider with its team" names the resource and signals single-record retrieval, which implicitly contrasts with the sibling naut_search_services. It is clear what is returned, though it never names the search alternative explicitly, so differentiation is by inference rather than statement.

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?

No when-to-use or when-not-to-use guidance is given; the agent must infer that this is for fetching a known provider by slug rather than discovering one. "Costs 5 credits" is decision-relevant context but is not framed as usage guidance (e.g., prefer this over search when you already have the slug).

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