Skip to main content
Glama

Florian Preisenhammer · AI Transformation Lead

Get service details

get_service
Read-onlyIdempotent

Get detailed information about a single area of work by id.

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

Input Schema

NameRequiredDescriptionDefault
idYesService id: ai-transformation | digital-products | prototypes | labs.

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, idempotentHint=true, and openWorldHint=false, so the safety profile is fully covered without description help. The description adds nothing beyond that: it does not mention behavior for unknown ids, what 'detailed' fields are returned, or any error handling. Given the rich annotation coverage, a baseline 3 is appropriate.

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?

A single efficient sentence with no wasted words and the retrieval target front-loaded. Minor cost from the vague phrase 'area of work' where 'service' would be immediately clearer.

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?

For a one-parameter read tool with full annotation coverage, no output schema, and complete schema descriptions, this is close to sufficient. The remaining gap is the absence of any hint about what the returned details contain or routing to sibling detail tools.

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 enumerates the accepted id values (ai-transformation | digital-products | prototypes | labs). The description only restates 'by id' and adds no format or selection guidance beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 detailed information about a single area of work by id.' This clearly distinguishes a single-item fetch from list_services and from siblings like get_insight or get_profile, though calling a service an 'area of work' is slightly indirect given the tool name.

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 guidance on when to use this versus siblings such as get_ai_engineering_practice or list_services, and no exclusions. The only implied usage is that an id must already be known, which comes from 'by id' rather than any explicit instruction.

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