Skip to main content
Glama
Sign In

Foundingbird

by com.foundingbird
OverviewDiscussionsAdmin

Redraft the business classification

regenerate_business_classification

Draft an incorporation's business description, name explanation and MSIC codes again, e.g. after the first draft failed or the customer wants fresh suggestions. Poll get_business_classification for the result.

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": {
      "application_id": "<application_id>"
    },
    "name": "regenerate_business_classification"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesThe application's id (obs_…), from list_applications or start_application.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations declare this as a non-read-only, non-idempotent mutation, and the description adds behavior that the annotations do not cover: this is an asynchronous operation whose result must be fetched by polling get_business_classification. It stops short of stating what happens to the previous draft or whether the redraft incurs cost.

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?

Two sentences, with the action and its outputs front-loaded and the trigger examples plus the polling instruction following. There is no redundant restatement of the title or schema.

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?

With no output schema and a single required parameter, the description covers what is generated and how to retrieve the result, which is the key operational fact. It is slightly incomplete on whether the prior classification is replaced and how long the redraft takes.

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?

There is only one parameter, and its schema description covers 100% of the schema, including the obs_… pattern and where to obtain it. The description adds no meaning beyond that, so the baseline of 3 applies.

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?

The description states a specific verb and resource: redraft an incorporation's business description, name explanation, and MSIC codes. It also implicitly distinguishes itself from the read-side sibling by telling the agent to poll get_business_classification separately, so an agent can tell the two apart without opening either schema.

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

Usage Guidelines4/5

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

It gives concrete triggers for use, such as when the first draft failed or when the customer wants fresh suggestions. It lacks an explicit when-not to use, such as a limit on redrafting or a conflict with submit_application, but the context is clear.

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

All Foundingbird toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources