Skip to main content
Glama

Public endpoints

dialect_endpoints
Read-onlyIdempotent

Use first: the endpoints anyone may read, each with its name and title. Side effects: none.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so "Side effects: none" restates structured data rather than adding to it. The one genuine addition is the disclosure that each entry carries a name and title, which matters because there is no output schema. No pagination or volume guidance is offered.

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 compact sentence pair with the routing instruction ("Use first") front-loaded and no filler. Every clause carries information about scope or output.

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 parameters, no output schema, and rich annotations, the description covers what the tool returns and when to reach for it. It could go one step further and note that the returned endpoints feed into dialect_read_endpoint, but nothing essential is missing.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. The mention of returned name/title fields is a return-value detail, not a parameter one.

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 endpoints anyone may read, each with its name and title" identifies the resource (endpoints), the scope (publicly readable), and the returned fields. The verb is implicit rather than stated as "list", but an agent can still tell this apart from dialect_read_endpoint, which targets a single endpoint.

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

Usage Guidelines4/5

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

"Use first" gives explicit ordering guidance relative to the sibling tools, which is exactly the routing signal an agent needs for a discovery call. It stops short of naming alternatives or stating when not to use it, but the sequencing instruction covers the main decision.

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