Skip to main content
Glama
Sign In
dtelecom-stt

dtelecom-stt

Official
by dTelecom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

stt_pricing

Check dTelecom speech-to-text pricing with no payment required. View current rates to plan your transcription budget.

Instructions

Get current dTelecom STT pricing information. No payment required.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are present, so the description carries the full burden. It conveys a read-only intent through 'Get' and adds the useful behavioral fact 'No payment required'. However, it does not disclose response format, data freshness, or any other operational constraints, though the simplicity of a zero-parameter pricing lookup reduces the risk.

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?

The description is extremely concise: one short main clause stating the action and resource, plus a brief relevant note about payment. Every word earns its place, and the core purpose is front-loaded.

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, no-output-schema tool this description is largely sufficient: it explains what the tool provides and that it is free. It could mention the exact shape of the returned pricing data, but the triviality of the tool lowers the burden on the description.

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 input schema has zero parameters, so there is nothing for the description to add about parameter meanings. The baseline for parameterless tools is 4, and the description appropriately provides context about the resource being queried.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Get' and clearly identifies the resource as 'current dTelecom STT pricing information'. This unambiguously distinguishes the tool from siblings transcribe_file and stt_health, which focus on transcription and health status respectively.

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?

The context is clear: the tool is for retrieving pricing information, and the note 'No payment required' clarifies that invoking it has no cost. It does not explicitly contrast with sibling tools, but the focused purpose makes the intended use easy to infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools