TradieBridge

Ask a question

ask_question

Read-only

Answer one of the questions the instructions name (discover_questions describes them) in one call, reading the source's copy server-side. arguments are the question's own; a missing or wrong one answers with the arguments it takes. Without connection_id every source that answers the question answers it, each under answers with its connection_id, connection, source and as_of: two sources measure different ledgers, so read them side by side and never add them. connection_id narrows to one source.

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

Input Schema

Name	Required	Description
`name`	Yes	The question's name, e.g. receivables.
`arguments`	No	The question's arguments. Omit for none.
`connection_id`	No	Only this source's answer; list_connections names them.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 14, 2026

removedInput schema / properties / build_id

Removed value: -{
-  "description": "Only this build's answer; list_connections names them.",
-  "type": "integer"
-}

addedInput schema / properties / connection_id

Added value: +{
+  "description": "Only this source's answer; list_connections names them.",
+  "type": "integer"
+}

First observedOct 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already carry the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false). The description adds meaningful context beyond them: execution happens server-side against the source's own copy, each answer carries connection_id/connection/source/as_of, and it warns that answers from distinct sources must never be summed because they measure different ledgers.

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?

The action is front-loaded and there is no filler, but the prose is a run-on tangle ('each under answers with its connection_id') that forces re-reading. Length is defensible for the concepts covered; readability is not.

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?

With no output schema, the description does the work of disclosing the response shape (per-source entries with connection_id, connection, source, as_of) and links to discover_questions and list_connections for the dependent lookups. Enough for an agent to call and interpret it, aside from not covering pagination or partial-failure behavior.

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%, so the baseline is 3, but the description adds behavioral semantics the schema cannot: 'arguments' belong to the named question and a missing/wrong argument elicits an error response listing the expected arguments, and connection_id scopes the result to a single source rather than filtering within one.

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?

The description uses a specific verb (answer) plus the resource (one of the named questions) and points at discover_questions for the question catalogue, which separates it from sibling read tools like get_record and search_records. It is clear what the tool does, though the dense phrasing blurs the edges a little.

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

Usage Guidelines4/5

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

It states that questions are enumerated by discover_questions, that connection_id narrows to one source, and that omitting connection_id fans out to every qualifying source. That is real when-to-use guidance, but it never says when a sibling (e.g. get_record or search_records) would be the better choice.

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

All TradieBridge 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?