Skip to main content
Glama

Mdexa

What Mdexa is and what it is worth

get_overview
Read-onlyIdempotent

Call when the user asks what Mdexa is or what it can do: what the database is, why it exists, what is distinctive, live figures (with as_of dates) and example queries. Factual, can be relayed as is. Not counted as a call.

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

Input Schema

NameRequiredDescriptionDefault
langNoen
hintsNo

Output Schema

NameRequiredDescriptionDefault
figuresNo
summaryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety needs no restating. The description adds genuinely new behavioral facts: content is factual and relocatable verbatim, figures are live and stamped with as_of dates (a freshness guarantee), and the call is not counted against quota. Only the semantics of the 'hints' toggle are left undisclosed.

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?

The trigger is front-loaded and the payload list follows immediately; the two trailing clauses ('Factual, can be relayed as is', 'Not counted as a call') are short and each carries distinct information. The single dense sentence is slightly packed but nothing is padded.

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?

An output schema exists, so the description is not obliged to explain return values, yet it usefully signals the content shape and the as_of dating. For a zero-required-parameter orientation tool this is close to complete; the only real omission is what 'hints' does and how 'lang' affects the response.

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

Parameters2/5

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

Schema description coverage is 0% for the two parameters. The description says nothing about 'lang', so an agent cannot tell that output language follows this flag, and it says nothing about 'hints' (enum on/off), whose effect is completely opaque. With zero coverage the description should compensate, and it does not.

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 enumerates the concrete payload: what the database is, why it exists, what is distinctive, live figures with as_of dates, and example queries. That is a specific, recognizable resource, though the verb is framed as a trigger condition ('Call when...') rather than a direct statement of what the tool returns. It is clearly distinct from the sibling search/get tools, which return records rather than orientation material.

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 trigger is explicit: 'Call when the user asks what Mdexa is or what it can do.' That covers the primary when-to-use case well. There are no exclusions or named alternatives, so an agent must infer that get_card/get_ledger_head etc. serve different questions, but the intent gap is small for an orientation tool.

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.