Skip to main content
Glama

SCRIPTMASTERLABS — Agent Verify

Open jobs on Bid-cast

board_search
Read-onlyIdempotent

Open, funded jobs on SML's Bid-cast board (escrow on Circle Arc), as published by the venue. Free, read-only; to post or bid, use Bid-cast itself (EIP-191 signed).

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

Input Schema

NameRequiredDescriptionDefault
capabilityNoCapability filter: return only open jobs whose required capability matches this string; omit to list every open funded job.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / capability / description
      Added value: +"Capability filter: return only open jobs whose required capability matches this string; omit to list every open funded job."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior context beyond that: no cost, escrow status of the underlying jobs, venue-published provenance, and that write actions exist only outside this tool. Return shape and result limits remain unstated.

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?

Two compact sentences with no filler. The core scope is front-loaded before the read-only and alternative-venue caveats, so the most decision-relevant information arrives first.

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 one-optional-parameter read tool with rich annotations and no output schema, the description covers scope, cost, provenance, and the write-path boundary. It would be stronger if it sketched what each job record contains or noted any result-count limits, since no output schema exists to fill that gap.

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?

The single optional capability parameter is fully documented in the schema (100% coverage, including the omit-to-list-everything semantics), so the schema carries the load. The description does not mention the capability filter at all, adding no meaning beyond the structured field. 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 names a concrete resource and narrows its scope precisely: open, funded jobs on SML's Bid-cast board, with escrow on Circle Arc, as published by the venue. An agent knows exactly what corpus it is querying. It stops short of an explicit listing verb and does not contrast with siblings like ledger_list or agent_records, so it is clear but not fully differentiated.

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?

It gives a clear when-not and a named alternative: posting or bidding belongs to Bid-cast itself via EIP-191 signed requests, not this tool. It also flags the tool as free and read-only, which sets expectations on cost and side effects. It does not address when to prefer this over the other read-only siblings, which is the remaining gap.

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