Skip to main content
Glama

The Local Upgrade — Software Engineering

Explore software engineering services

discover_services
Read-onlyIdempotent

Full-stack products, agent systems, integration, modernization and B2B engineering workstreams. Returns service scope and engagement options.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds useful return context ('service scope and engagement options'), which matters because there is no output schema. It says nothing about auth needs, rate limits, or pagination, so it adds moderate rather than rich value.

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 with no filler, and the return information is placed last as a natural close. The first sentence is a bare noun-list without a verb, which reads slightly telegraphic, but it is efficiently sized for the tool's simplicity.

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 zero-parameter, read-only discovery tool with full annotation coverage and no output schema, the definition is largely sufficient: it conveys both the domain scope and the shape of the response. The main missing piece is any hint about when to reach for this versus the engagement/proposal siblings.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 regardless of description content. There is nothing parameter-related the description could usefully add or omit.

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?

The description names the concrete service domains (full-stack products, agent systems, integration, modernization, B2B workstreams) and states the return ('service scope and engagement options'), so an agent grasps that this is a catalog/discovery tool. It does not explicitly contrast with siblings like review_engineering_evidence or get_procurement_information, keeping it below 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 explicit when-to-use or when-not-to-use guidance, and no alternative is named. The only signal is the tool name 'discover_services' plus the list of domains, which merely implies a first-touch exploration step rather than stating it.

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