Skip to main content
Glama

companies_request_reseller

Destructive

Submits a request to grant reseller status for a specified company using its company ID.

Instructions

Request reseller status for company POST /companies/{id}/reseller/request

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

Input Schema

NameRequiredDescriptionDefault
idYesCompany ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing behavioral beyond that: it doesn't say what the request triggers, whether it can be repeated, what state change or approval process results, or whether it is reversible.

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?

Extremely short and front-loaded with the action. The raw 'POST /companies/{id}/reseller/request' line is largely redundant with the tool name and schema, though it does confirm the target resource.

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

Completeness3/5

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

For a single-parameter mutation with full schema coverage and full annotation coverage, the essentials are present. However, a destructive-flagged request tool would benefit from saying what the request submits and what state it leaves the company in, which is absent.

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?

Only one parameter, and the schema already documents it at 100% coverage ('Company ID'). The description's path template merely restates that the id is a company identifier and adds no format or constraint detail. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource: 'Request reseller status for company', which separates it from the sibling companies_request_kyb. It doesn't explicitly name alternatives, but the resource is unambiguous enough for selection.

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

Usage Guidelines2/5

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

No when-to-use guidance, no preconditions (e.g. must the company exist, must the caller be an owner, is there an approval flow), and no mention of when to prefer companies_request_kyb or companies_update_company instead. The agent must infer everything from the name.

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