Skip to main content
Glama

Cobalt Tin Verify

cobalt_tin_verify
Read-onlyIdempotent

Verify a business TIN/EIN against IRS records, confirms a 9-digit EIN matches the legal business name on file with the IRS. Returns match status, IRS code/reason and last-checked date. Synchronous (<5s). Example: cobalt_tin_verify({ tin: "123456789", businessName: "Acme Corp", _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tin": "123456789",
      "_apiKey": "your-cobalt-api-key",
      "businessName": "Acme Corp"
    },
    "name": "cobalt_tin_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
tinYesThe 9-digit EIN/TIN, digits only (no dashes), e.g. "123456789".
_apiKeyYesCobalt Intelligence API key.
businessNameYesThe legal business name exactly as filed with the IRS.

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 declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavioral context: it is synchronous and returns in under 5 seconds, and it enumerates the return payload (match status, IRS code/reason, last-checked date). It omits failure semantics (what happens on no-match or IRS outage), which keeps it below 5.

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?

The core purpose is front-loaded in the first clause and the example gives an immediately actionable call shape. There is mild redundancy in restating 'TIN/EIN' then '9-digit EIN', and the opening sentence is a comma splice, but nothing is wasted enough to penalize further.

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 3-required-parameter tool with no output schema, the description covers what is needed to call it correctly and summarizes the return values without an output schema. Latency expectation is a useful addition. It lacks any note on error/no-match behavior or API-key acquisition, which would complete the picture.

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 description coverage is 100%, so all three parameters (tin, businessName, _apiKey) are already documented with format constraints in the schema itself. The description's only added nuance is the 'exactly as filed with the IRS' emphasis on businessName and the example value format, which largely restates the schema; 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?

Uses a specific verb+resource pair ('Verify a business TIN/EIN against IRS records') and states the exact check performed: a 9-digit EIN matching the legal business name on file with the IRS. It does not name or differentiate itself from nearby siblings such as cobalt_business_search or cobalt_ucc, so it falls short of a 5.

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 purpose and by the inline example call, which shows the intended invocation shape. However, there is no explicit when-to-use/when-not-to-use guidance and no mention of the alternative cobalt tools an agent might pick instead for business lookup vs TIN validation.

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.