Skip to main content
Glama

Read a data-licensing offer

read_data_offer
Read-onlyIdempotent

Reads a pasted data-licensing offer and returns what it finds, with the offer's own words quoted back: the figure set against the published span, the payment trigger, exclusivity, export method and data retention — each reported as stated or as not stated — plus the terms worth settling before signing and the question to ask on each. A term the offer is silent on is reported as a finding, not filled in. Nothing is stored, and this is not legal advice.

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

Input Schema

NameRequiredDescriptionDefault
offerYesThe offer text: a term sheet, an email, or the part to be read.
yearsNoYears of records. Omit if unknown.
headcountNoFull-time employees, so the price is set against the programs this company clears. Omit if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral facts: silence on a term is reported as a finding rather than filled in, the offer's own words are quoted back, nothing is stored, and it is not legal advice. The non-hallucination policy and the disclaimer are exactly the kind of context structured fields cannot carry.

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?

Front-loaded with the verb and the return contents, then closed with the two caveats. The mid-sentence enumeration is dense but every item is a real extraction target, so nothing is clearly wasteful; a bulleted or shorter phrasing would read better.

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?

There is no output schema, and the description compensates fully by describing the structure of the return: per-term findings marked as stated or not stated, terms to settle before signing, and a question for each. Combined with the schema handling the three inputs, an agent has what it needs to call this correctly.

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 description coverage is 100%, with all three parameters documented including the 'omit if unknown' guidance for years and headcount. The description adds no further parameter meaning beyond noting that the figure is read 'against the published span', so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('reads a pasted data-licensing offer') and then enumerates exactly what it returns: figure versus published span, payment trigger, exclusivity, export method, retention. That level of specificity clearly separates it from the sibling tools, none of which parse offer text.

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 implied by 'pasted' offer text and the enumeration of the terms it reads, so an agent can infer this is the intake-and-parse step. However, it names no alternatives and gives no explicit when-not-to-use criteria or prerequisites (e.g., what counts as a complete-enough offer to submit).

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