Skip to main content
Glama

Ca Procurement

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. Description adds scope (anonymous IP, hash, account ID) and behavior when no key is provided, going beyond annotations.

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?

Three sentences, no fluff. First sentence gives core function, second provides usage context, third adds scope and pairing. Efficiently front-loaded.

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?

Simple tool with 1 optional param and no output schema. Description explains purpose, usage, and scope sufficiently. Return format is implied but not detailed, acceptable for this 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?

Schema coverage is 100% for the single parameter. Description adds clarity that omitting the key lists all saved keys, which is not in the schema description.

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?

Description clearly states the tool retrieves a value saved via 'remember' or lists all keys if omitted. Specific verb+resource and distinguishes from sibling tools (remember, forget).

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?

Provides clear context: use to look up previously stored data without re-deriving. Mentions pairing with remember and forget, but does not explicitly state when not to use.

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

All Ca Procurement toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation1/5

The tool set has severe overlap: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve similar query/discovery purposes, and multiple polymarket tools (polymarket_edges, polymarket_arbitrage, bet_research) overlap heavily in finding betting opportunities. An agent would struggle to select among these without deep familiarity, especially when ask_pipeworx and ask_pipeworx_beta are currently identical.

Naming Consistency2/5

Individual families are internally consistent (ca_procurement_*, polymarket_*, pipeworx_*), but the server as a whole mixes domain-prefixed snake_case, bare verb phrases (ask_pipeworx, bet_research), and descriptive noun phrases (entity_profile, recent_changes). More importantly, the vast majority of tool names have nothing to do with the server's stated 'Ca Procurement' identity, so the naming fails to signal a coherent tool set.

Tool Count2/5

36 tools is well past the 25+ threshold for 'too many,' and over 85% of them (31 tools) are unrelated to California procurement—they cover general data lookup, prediction markets, npm packages, and memory storage. A scoped CA procurement server would reasonably have 5–8 tools; this is a general-purpose data platform wearing a procurement label.

Completeness3/5

The five relevant ca_procurement_* tools cover the main read-side query patterns well: award search, commodity rankings, department profiles, supplier aggregation, and top suppliers. However, the surface lacks contract/award detail retrieval by ID, solicitation or RFP search, and any vendor registration or contract lifecycle data, leaving notable gaps for a procurement-focused tool set.

Resources