Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

tender_search

[PAID $0.02 USDC/call, x402, eip155:8453] Search live public procurement notices from the official French register: object, buyer, department, procedure, publication date, deadline and the canonical BOAMP link. Signed, so a bid decision can be proved later.

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

Input Schema

NameRequiredDescriptionDefault
qNoFree text searched in the tender object (e.g. logiciel, nettoyage)
daysNoOnly notices closing within N days
deptNoFrench department code, 1-3 digits (e.g. 75)
limitNoMax notices returned (1-50, default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses a per-call cost ($0.02 USDC via x402 on eip155:8453), names the authoritative source register, and states responses are signed for later proof. Missing only operational details such as rate limits, freshness cadence, or error behavior.

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 compact sentences with the payment/access model front-loaded in brackets, which is the right priority for an agent that must budget a paid call. No filler, though the result-field enumeration is dense enough to be slightly hard to parse.

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?

For a 4-parameter, all-optional search tool with no output schema, the description usefully stands in for one by naming the returned fields, and it covers cost, protocol, provenance and signing. Only the relationship to the closely related 'tender_deadlines' tool is unaddressed.

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%, so the schema already explains q, days, dept and limit with examples. The description adds nothing about parameter semantics — the field list describes results, not inputs — so the baseline 3 applies.

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 gives a specific verb and resource ('Search live public procurement notices from the official French register') and enumerates the fields returned (object, buyer, department, procedure, dates, BOAMP link). It does not distinguish the tool from the sibling 'tender_deadlines', which an agent would need spelled out to choose correctly.

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: the word 'Search' plus the presence of q/dept filters suggests keyword or location lookups. There is no explicit statement of when to pick this over 'tender_deadlines', no prerequisite or eligibility notes, and no guidance on empty-result situations.

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

All Novarithm Agent Hub: trust and commerce checks toolsInspect
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