centric-demo

get_radar

Get the Relational IP™ radar shape for a demo contact: five axes, each a red, yellow or green status plus a normalized 0–1 position for rendering the widget. Intentionally returns no numeric score.

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": {
      "contact": "<contact>"
    },
    "name": "get_radar"
  }
}

Input Schema

Name	Required	Description	Default
`contact`	Yes	Contact id or name, e.g. 'Isabella Chen'

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedJul 7, 2026

TDQS

B3.4/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 burden. It does add real value by disclosing that the tool 'Intentionally returns no numeric score' and describing the axis/status/position output shape, but it says nothing about behavior when a contact is missing, whether it only works for demo contacts, or any auth/rate constraints.

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, output shape front-loaded, and the caveat about no numeric score placed where it matters. No filler or repetition of the tool name.

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?

There is no output schema, so the description must describe the return value, which it does (five axes, status colors, normalized position). It is nearly complete for a single-parameter read tool, missing only error/missing-contact behavior and the demo-contact restriction's implications.

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?

Only one parameter and schema description coverage is 100%, so the schema already explains that 'contact' accepts an id or name with an example. The description adds the qualifier 'demo contact' but no further semantics beyond that; 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?

Names a specific verb and resource ('Get the Relational IP™ radar shape for a demo contact') and enumerates the shape of what comes back: five axes, red/yellow/green status, normalized 0–1 position. It does not explicitly distinguish itself from siblings like get_contact_profile, which is the main gap.

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?

The phrase 'for a demo contact' hints at scope but never states when to call this versus get_contact_profile, brief_me, or the other siblings, and gives no prerequisites or exclusions. The agent must infer selection from the name alone.

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

All centric-demo 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?