Bloki.si

What the data cannot answer

data_limitations

Read-onlyIdempotent

List what this data CANNOT answer, and the nearest thing it can. INPUT: nothing. READ: limitations — nineteen questions with a stated reason and a substitute. NEVER: infer an answer the register does not hold. Absent here: days on market, who owns a private flat, whether a flat is renovated, drive times, a building manager's fee or service record. THEN: call this when a user asks for one of those, instead of estimating. Free to call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "data_limitations"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`note`	Yes
`as_of`	Yes
`limitations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, so the description's added value is the payload shape ('nineteen questions with a stated reason and a substitute'), the explicit prohibition on inference, and the cost note ('Free to call'). That is nearly everything an agent needs behaviorally, though it does not say what an empty or unmatched result looks like.

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?

Labelled INPUT/READ/NEVER/THEN lines front-load the decision-relevant content and every line carries distinct information — trigger, payload, prohibition, cost. Nothing repeats the schema or the title verbatim.

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

Completeness5/5

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

An output schema exists, so return values need not be spelled out, yet the description still sketches the register's structure. For a zero-argument, read-only, no-cost tool this leaves nothing material missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the baseline is 4; the description confirms this explicitly with 'INPUT: nothing', removing any doubt raised by the empty schema. No further parameter meaning is possible.

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?

States a specific verb and resource — 'List what this data CANNOT answer' — which no sibling tool covers; the sibling names (asking_prices, property_history, find_owner, etc.) are all positive lookups, so the negative-space tool is unambiguous. The title and first sentence agree and add the useful 'and the nearest thing it can' scope.

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

Usage Guidelines5/5

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

Explicit routing: 'call this when a user asks for one of those, instead of estimating' names both the trigger condition and the forbidden alternative (estimation). The NEVER line reinforces when not to fabricate an answer. No sibling tool competes for this call.

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

All Bloki.si 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?