Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

Get panel feasibility / status

get_feasibility
Read-only

Fetches provider operations snapshots from Cint, Dynata, or Bilendi admin status routes for panel feasibility checks; admin access is required.

Instructions

Fetch a provider ops snapshot from the existing admin routes (cint/status, dynata/status, bilendi/projects). These routes return 403 for non-admins. There is no separate member feasibility route.

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": "get_feasibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerNoPanel provider (default cint)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful behavior the annotations lack: an authorization gate (403 for non-admins) and the underlying admin routes. It does not describe response shape or failure modes beyond the 403.

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?

Three short sentences, front-loaded with the core action, then the auth caveat, then the scope clarification. Nothing is padded, though the last sentence is a minor aside rather than essential.

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

Completeness3/5

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

For a single-optional-param read tool with no output schema, the description covers where data comes from and who can call it. It still leaves the return contents ('ops snapshot') undefined, which matters since no output schema exists to compensate.

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?

Schema coverage is 100% and the provider enum with its cint default is fully documented there. The description still adds value by mapping each provider value to the specific route it hits (cint/status, dynata/status, bilendi/projects), which the schema does not convey.

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 specific verb+resource ('Fetch a provider ops snapshot') and names the concrete backing routes for each provider, so an agent knows what data actually comes back. The wording drifts from the name 'feasibility' to 'ops snapshot', which is a small ambiguity, but the route mapping compensates.

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?

The 403-for-non-admins note gives an implicit when-not-to-use condition, and the final sentence clarifies there is no member-level alternative. It does not point to any sibling tool (e.g., list_panel_projects) as the alternative path, so routing guidance is only partial.

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