Skip to main content
Glama

Tommos

Rename a company

rename_a_company
Idempotent

Change the name of a company, as the signed-in person, as the company's page does: at most 300 characters, spaces folded to one. A person's name stays: no later find of a module writes the name again. The rename is a line of the company's history and of the audit trail.

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": {
      "company_id": "<company_id>",
      "name": "<name>"
    },
    "name": "rename_a_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe company's new name
company_idYesThe company's id (from list_companies)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive behavior, and the description adds real context beyond them: the 300-character cap, whitespace folding, that person names are left untouched, and that the rename is recorded in company history and the audit trail.

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?

Three short sentences, front-loaded with the action and its constraints. The clause "no later find of a module writes the name again" is awkwardly worded and slightly obscures the point, 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?

For a two-parameter mutation with annotations and no output schema, the description covers constraints, side effects, and audit consequences. Only the response shape and permission requirements are left unstated, which is minor here.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds constraints on the name parameter (max 300 characters, spaces folded to one) that the schema does not state, plus the note that person names are unaffected.

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?

States a specific verb and resource ("Change the name of a company") and scopes it to the signed-in person acting as the company's page does, which separates it from siblings like move_a_company or link_a_person_to_a_company.

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?

Usage is implied by the verb and the actor scoping, but there is no explicit when-to-use/when-not guidance and no named alternative for related operations such as moving a company.

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.