Agent.chain.tokyo Address Contracts

Check virtual floor availability

get_floor_availability

Check a virtual floor for the authenticated owner without disclosing another owner's identity.

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": {
      "locationId": "<locationId>",
      "floor": "<floor>"
    },
    "name": "get_floor_availability"
  }
}

Input Schema

Name	Required	Description	Default
`floor`	Yes
`locationId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

C2.6/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses a non-obvious privacy trait (no disclosure of another owner's identity), but omits whether the operation is read-only, what permissions are required, what happens on an unavailable floor, and what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single efficient sentence with no wasted words, but its brevity comes at the cost of under-specification rather than disciplined front-loading. The privacy caveat is useful but arrives before the basic purpose is clearly established.

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

Completeness2/5

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

Given the absence of annotations, output schema, and schema descriptions for both parameters, the description is too thin to fully support correct invocation. It does not explain what 'availability' means in the response or how locationId and floor interact, leaving significant gaps.

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?

Both required parameters (locationId, floor) have 0% schema description coverage, and the description provides no explanation of their meaning, format, or correlation. It does not compensate for the schema gap, leaving the agent to infer parameter behavior solely from names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('a virtual floor') and a vague verb ('check'), but 'check' does not specify what is being checked — the title and tool name carry the missing 'availability'. It does not differentiate from siblings, though none of the listed siblings are similar.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no indication of what to do when a floor is unavailable. The only context is the privacy constraint, which is a behavior, not a usage rule.

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

All Agent.chain.tokyo Address Contracts tools Inspect

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

Need Help?