Skip to main content
Glama

get_notice

Retrieve a cached public procurement notice by source and number to access its lots and document-platform URL.

Instructions

Read one cached notice, including its lots and document-platform URL; identity is source plus number.

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": {
      "source": "<source>",
      "number": "<number>"
    },
    "name": "get_notice"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYes
sourceYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses a meaningful trait — the notice is cached, implying possible staleness — and previews the returned fields, but says nothing about permissions, not-found behavior, or freshness guarantees.

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 front-loaded sentence with no filler: purpose, cached nature, return highlights, and the keying rule all land in one pass.

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?

An output schema exists, so return values needn't be detailed. However, for a two-required-parameter lookup tool with zero annotation coverage and zero schema parameter descriptions, the description leaves gaps around valid `source` values, caching semantics, and failure modes.

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 0%, so the description must compensate for both parameters. It does add real meaning by stating identity is "source plus number" (a composite key), but leaves the accepted `source` values/format and the notice-number format undocumented.

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 resource ("Read one cached notice") with the returned payload called out (lots, document-platform URL). The singular "one" implicitly distinguishes it from search_notices, but no sibling is named explicitly.

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: "one cached notice" signals a single-record fetch where search_notices would be the multi-record path, but the description never states when to prefer this tool or what happens if the notice is not cached.

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