Skip to main content
Glama

SOQVER business facts (SO4AG)

Get claims for a task

get_claims
Read-only

Return claims of a source evaluated for a task: property (e.g. refundableDeposit, totalPrice, acceptedPaymentMethods) and scope (e.g. {"branch": "...", "vehicle_class": "economy"}). Each claim says whether it is usable now and why not.

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_claims"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
scopeNo
propertyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's added value is the disclosure that each claim carries a usability verdict and a reason. That is useful beyond the annotations, but result size, pagination, and behavior when filters match nothing are unstated.

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?

Two tight sentences with the core purpose front-loaded and examples kept inline. The colon-and-example structure is slightly dense but nothing is redundant.

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?

With no output schema, the description does explain the shape of a claim's verdict ('usable now and why not'), which is the right call. It still leaves the required source identifier and the filtering/pagination behavior of a nested-object query unexplained for a three-parameter tool.

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?

With schema description coverage at 0%, the description does real work: it illustrates the property vocabulary (refundableDeposit, totalPrice, acceptedPaymentMethods) and shows scope as a key/value object such as {"branch": "...", "vehicle_class": "economy"}. It never mentions the required slug parameter or states explicitly that property and scope are filters, which keeps it short of a 5.

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 names a specific verb and resource ('Return claims of a source evaluated for a task') and grounds it with concrete examples of the property and scope dimensions. It does not distinguish this tool from the singular sibling check_claim or get_source, leaving the boundary implicit.

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?

There is no when-to-use statement, no exclusions, and no named alternative. The phrase 'evaluated for a task' hints at context but gives no rule for choosing this over check_claim or get_source.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources