Skip to main content
Glama

Maple Minute

Get a company

get_company
Read-onlyIdempotent

One company in full: status, what it is waiting for, corporation number, company email, documents, government mail and change requests.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCompany id like MM-12, from list_companies.

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 cover the safety profile (readOnlyHint, idempotentHint), so the bar is lower. The description adds real value by enumerating what the response contains, which matters because there is no output schema to document it. It does not say what happens on an unknown or malformed id, which is the main remaining gap.

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?

A single compact sentence with the resource front-loaded and the returned fields enumerated after a colon. No wasted words, though the telegraphic fragment style ('what it is waiting for') trades a little clarity for density.

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 one-parameter idempotent read with no output schema, the definition supplies the essential missing piece: the shape of what comes back. Structure of the returned object (nesting, ordering, pagination of documents or change requests) remains unspecified, which is the only notable omission.

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

Parameters3/5

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

Schema coverage is 100% and the schema itself documents the single id parameter, including its MM-12 format and its origin in list_companies. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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 identifies the resource precisely and enumerates what 'full' contains: status, corporation number, email, documents, government mail and change requests. 'One company' implicitly distinguishes it from list_companies, which returns many. It lacks an explicit verb, relying on the title 'Get a company' to supply it.

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

Usage Guidelines3/5

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

There is no 'use this when...' statement and no exclusions. The only usage signal is indirect: the description says nothing about alternatives, though the schema note that id comes 'from list_companies' implies the list-then-fetch sequence. An agent can infer the pattern but the description does not state 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