Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Get Business Name Renewal Status

get_business_name_renewal_status
Read-only

Track a business-name renewal from submission to completion using a request ID; returns progress and the transaction document link.

Instructions

Status of a business-name renewal: new -> … -> finished with response {transactionDocumentUrl, businessNameNumber, renewalTo}.

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": {
      "request_id": "<request_id>"
    },
    "name": "get_business_name_renewal_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the description's burden is lower. It adds genuine behavioral context with the state progression (new -> … -> finished), but the ellipsis swallows the intermediate states and nothing is said about polling cadence, terminal failure states, or eventual consistency. The inline response field list duplicates the existing output schema rather than adding new behavioral information.

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 front-loaded sentence with no filler, and the state machine is placed first. The compressed "new -> … -> finished" arrow notation and inline JSON braces are slightly cryptic compared with plain prose, but nothing is wasted.

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 one-parameter read tool with a full output schema and readOnly annotation, the core is present: the resource, the lifecycle, and the return shape are all signaled, so an agent could call it. However the undefined request_id and the unenumerated terminal states leave real gaps for a status-polling tool whose whole purpose is knowing when it is done.

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?

With schema description coverage at 0% and a single required integer request_id, the description carries the full explanatory burden and discharges none of it — it never mentions request_id, what it identifies, or where an agent obtains it (presumably the response of lodge_business_name_renewal). An agent must guess the parameter's provenance.

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?

"Status of a business-name renewal" names a specific resource and implicitly the read-status verb, which cleanly separates it from siblings such as get_business_name_registration_status and get_company_name_change_status. It stops short of an explicit verb (e.g. "Retrieve the status of…") and never names the counterpart lodge_business_name_renewal, so differentiation is inferred from the resource noun alone.

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 only implied: an agent can infer this is a polling/status-check tool to call after a renewal is lodged, but the description never says when to call it, whether it should be polled repeatedly, or that lodge_business_name_renewal is the prerequisite. There are no explicit exclusions or alternatives given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.