Skip to main content
Glama

Check registration status

check_status
Read-onlyIdempotent

Looks up where a registered company is in Datari Labs' pipeline, by the work email used at registration. Read-only.

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": {
      "work_email": "<work_email>"
    },
    "name": "check_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
work_emailYesThe work email used when the company registered

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the trailing 'Read-only' mostly restates structured data. The description does add that lookup is keyed strictly on the registration email, but it says nothing about the lookup being exact-match only or what the agent should expect when no matching registration exists.

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?

One compact sentence that front-loads the verb and scope, plus a short qualifier. The final 'Read-only' is redundant against the annotations and could be dropped, keeping it just short of ideal.

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 one-parameter, non-destructive lookup this is close to sufficient: the agent knows the key, the scope, and the safety profile. The residual gap is that there is no output schema, so a hint about what 'status' looks like (stage name, enum of states, or not-found result) would have made it fully self-contained.

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 coverage is 100% and the single parameter's schema description already says 'the work email used when the company registered.' The description's restatement adds the nuance that this must be the registration-time email rather than any contact address, but nothing about format, case sensitivity, or matching behavior, so the 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?

States a concrete verb and resource: it looks up a registered company's position in Datari Labs' pipeline, scoped to the email used at registration. That is clearly distinct from register_company and about_datari, though it never explicitly contrasts itself with check_fit, which an agent could plausibly confuse with a status check.

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: the phrase 'registered company' and 'the work email used at registration' tell the agent this applies after registration and requires the registration email as the key. There is no explicit statement of when to prefer this over check_fit, or what to do if the email was never registered.

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.

Resources