Skip to main content
Glama

AgentSupply

Get service details

get_service
Read-only

Get full details for one service: inputs, outputs, fulfilment, turnaround and indicative pricing.

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": {
      "service_id": "<service_id>"
    },
    "name": "get_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
service_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 the safety profile is covered. The description adds genuine context by disclosing which attribute groups the response includes (inputs, outputs, fulfilment, turnaround, pricing), but says nothing about error behavior for an unknown service_id or how pricing values are qualified as 'indicative'.

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?

A single front-loaded sentence with a compact enumerated list of returned content — no filler, no restatement of the title alone. Every clause conveys information an agent needs.

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

Completeness4/5

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

With no output schema, the description carries the burden of describing return content and does so by naming the five content areas. For a simple one-parameter read operation with read-only annotations, that is close to sufficient; only the origin of service_id is left unaddressed.

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?

There is one required parameter with 0% schema description coverage, so the schema itself provides no meaning for service_id. The description only implies it must identify a single service; it gives no format or provenance hint (e.g. where an ID is obtained, such as from list_services), so it fails to fully compensate for the coverage gap.

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 ('Get full details for one service') and enumerates the content areas returned: inputs, outputs, fulfilment, turnaround and indicative pricing. This is clearly distinct from a bulk listing, but the description never names list_services as the plural sibling, so the differentiation is inferential rather than explicit.

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

Usage Guidelines3/5

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

Usage is implied by 'for one service' — an agent can infer this is the detail lookup versus a list operation — but there is no explicit when-to-use statement and no named alternative. No prerequisites or exclusions are given, leaving routing to inference.

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