Skip to main content
Glama

OdileM2M network

get_m2m_network
Read-onlyIdempotent

Read the OdileM2M network card for Direct: the live skills a business can accept, what each costs in credits, the credit packs, the limits that apply, and the Gate MCP address and quickstart. Use it to cost Direct tasks before sending any. For your own balance use get_direct_usage. Returns the pricing card (currency, credit_cents, packs, lookups) plus live_skills[{id, name, description, credits}], receipts, mcp_url, gate_mcp_url, quickstart_url, docs_url and connect_steps[]. Reference data, nothing account-specific: takes no arguments, needs no sign-in, contacts no business and changes nothing. Example: call it once with no arguments before the first send_to_business of a session.

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_m2m_network"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.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 and closed-world, and the description adds genuine context beyond them: no sign-in required, no business is contacted, nothing changes, and a full inventory of return fields (pricing card, live_skills, receipts, URLs, connect_steps) which the tool otherwise lacks since there is no output schema. The "changes nothing" and "reference data" clauses partly restate the annotation hints rather than extend them, keeping it short of a 5.

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?

Purpose is front-loaded in the first clause, then cost-usage guidance, then the return inventory, then a worked example — a deliberate progression. The dense colon-list is doing real work rather than padding, since the return fields would otherwise be undocumented.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-argument reference tool with no output schema, the description supplies exactly what is missing elsewhere: the return shape, the lack of auth, and the timing of the call in the session workflow. Nothing an agent needs in order to invoke it correctly is absent.

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?

Zero parameters, so the baseline is 4, and the description reinforces it by stating the tool "takes no arguments," which removes any doubt about supplying an identifier. There is no further parameter meaning to add because none exist.

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?

A specific verb and resource ("Read the OdileM2M network card for Direct") followed by an enumeration of exactly what the card contains: live skills, credit costs, credit packs, limits, Gate MCP address and quickstart. It also names the sibling it is not (get_direct_usage), so an agent can separate it from balance lookups without opening a schema.

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

Usage Guidelines5/5

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

States the operative moment explicitly: "Use it to cost Direct tasks before sending any," routes balance questions to get_direct_usage, and closes with a concrete example of calling it once with no arguments before the first send_to_business of a session. When-to-use, when-not-to-use and an alternative are all present.

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