Deep Thought Consultech

get_product

Full detail for one DTC product: what it does, who it is for, how it deploys, and its FAQ.

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": {
      "slug": "<slug>"
    },
    "name": "get_product"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	One of: communication-bot, file-manager-agent, comment-insights, proactiveguard.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose what the response contains (capabilities, audience, deployment, FAQ), which substitutes for the absent output schema, but it says nothing about failure behavior for an unrecognized slug or about whether the detail is cached or complete.

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?

A single sentence that front-loads the outcome ('Full detail for one DTC product') and then itemizes the payload. Nothing is redundant or padded, and the colon-list structure is easy to scan.

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 lookup with no output schema and no annotations, the description conveys both scope and returned content, which is close to sufficient. The remaining gap is routing: the caller gets no help distinguishing this from the similarly named which_product sibling, and nothing is said about invalid-slug behavior.

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 slug parameter already lists its allowed values inline. The description adds no format, casing, or resolution rules beyond that enumerated list, so the schema is doing all the parameter work. Baseline 3 is appropriate.

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 and scope: 'Full detail for one DTC product,' which separates it from list-style siblings by emphasizing 'one.' It then enumerates the content returned (what it does, who it is for, deployment, FAQ). It never names which_product or list_products, so differentiation is implied rather than explicit.

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 by the phrase 'one DTC product,' which suggests single-item lookup rather than enumeration or search. There is no explicit when-to-use, no exclusion, and no pointer to the sibling tools (which_product, search_dtc, list_products) that a caller must choose between.

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

All Deep Thought Consultech 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?