ABS Data (observed)

Open a feedback form

feedback_form

Read-onlyIdempotent

Open a feedback form for the person, prefilled with your draft, so they can report a problem or suggest an improvement to this ABS connector — or flag something wrong in ABS's own data. Use it whenever the person wants to give feedback, or agrees when you offer after something went wrong. Fill in what you know from the conversation: kind, a one-line summary in their words, details, and the tool, table, selection and error involved. Never include personal information about anyone, and never fill in a contact email the person did not give you. This tool sends nothing: on hosts that show interactive views the person reviews, edits and sends the form themselves; elsewhere, follow the next field.

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

Input Schema

Name	Required	Description	Default
`kind`	No	bug: something broke; data: a figure or label looks wrong; missing: an expected table or option is absent; idea: an improvement; docs: unclear guidance; praise: it worked well; other
`tool`	No	The tool involved, e.g. get_data
`about`	No	connector: this connector or its site; abs: ABS's own data or API (so it can be passed on to ABS)	connector
`error`	No	The error reason or message returned, if any
`table`	No	The ABS table id involved, e.g. CPI
`contact`	No	Only if the person chose to give an email address for a reply. Never guess or fill one in.
`details`	No	What happened and what was expected. No personal information about anyone.
`summary`	No	One line, in the person's own words
`assistant`	No	The AI tool in use, e.g. Claude, ChatGPT, Copilot
`selection`	No	The selection or query involved, as JSON or the SDMX key
`shareWithAbs`	No	Only true if the person agreed this may be passed on to ABS, contact address included

Output Schema

Name	Required	Description	Default
`next`	Yes
`draft`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description explains why: "This tool sends nothing" and the person reviews, edits and sends the form themselves. It goes further with privacy constraints ("Never include personal information about anyone, and never fill in a contact email the person did not give you") that no annotation could convey.

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?

Purpose is front-loaded in the first sentence, followed by trigger guidance, field guidance, privacy rules and sending behavior in a logical order. It is longer than most definitions but nearly every sentence adds distinct information; a slightly tighter phrasing could merge the privacy warnings.

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?

For an 11-parameter, all-optional tool with a full output schema, the description covers purpose, when to use, what to fill in, privacy limits, and exactly what the call does and does not do. The one return detail it mentions (`next`) is documented by the output schema, so nothing an agent needs to invoke this correctly is missing.

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 description coverage is 100%, so the baseline is 3, but the description adds real meaning by naming which fields to populate from the conversation (kind, summary in their words, details, tool, table, selection, error). It also imposes a constraint on the contact and shareWithAbs fields that goes beyond the schema wording.

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?

"Open a feedback form for the person, prefilled with your draft" states a specific verb and resource, and the clause "so they can report a problem or suggest an improvement ... or flag something wrong in ABS's own data" scopes the purpose. It implicitly separates itself from the sending path ("This tool sends nothing") but never names the sibling submit_feedback, so the differentiation is inferred 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 Guidelines4/5

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

"Use it whenever the person wants to give feedback, or agrees when you offer after something went wrong" gives a concrete trigger condition, and "Fill in what you know from the conversation" specifies the prep step. The contrast with hosts that show interactive views versus "elsewhere, follow the `next` field" clarifies the downstream path, though the actual alternative tool submit_feedback is not called out.

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

All ABS Data (observed) 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.