Skip to main content
Glama

Iso

by io.github.pipeworx-io

Search Standards

search_standards
Read-onlyIdempotent

Search the full ISO catalogue (~all deliverables) by keyword across reference, title and abstract, with optional filters. Returns reference, title, status, abstract snippet, committee and the iso.org link. Use to find standards on a topic ("supply chain security", "medical device risk").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
icsNoFilter by ICS classification code prefix, e.g. "35.030" (IT security).
typeNoFilter by deliverable type: IS, TR, TS, PAS, Guide, …
limitNoMax results (default 20, max 50).
queryYesKeywords matched against title + abstract + reference (full-text).
statusNoFilter by publication status (prefix match).
committeeNoFilter by owner committee, e.g. "JTC 1/SC 27" (substring).

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds that it returns specific fields like reference, title, status, abstract snippet, committee, and iso.org link, providing behavioral context beyond the 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?

The description is two sentences, front-loaded with the action, and every sentence adds value. No wasted words.

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?

The description covers the tool's purpose, return fields, and example usage. While it doesn't mention pagination or default limit, the schema covers those details. Given no output schema, the description is sufficiently complete for an agent to use the tool.

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 100%, so baseline is 3. The description does not add additional parameter-level information beyond what the schema already provides; it only mentions optional filters in general terms.

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?

The description clearly states it searches the full ISO catalogue by keyword across specific fields (reference, title, abstract) and lists return fields. It distinguishes from siblings like 'get_standard' by specifying it's a search tool for finding standards on a topic.

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?

The description explicitly says 'Use to find standards on a topic' and provides example queries. It does not explicitly mention when not to use or alternatives, but the context is clear enough for an agent to decide.

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

All Iso 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.6/5.0
Disambiguation3/5

Tools are mostly distinct but there is some overlap among lookup tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, entity_profile) and among Polymarket tools (bet_research, polymarket_edges, polymarket_arbitrage). Agents might occasionally struggle to choose the right one.

Naming Consistency2/5

Naming is inconsistent: some use verb_noun snake_case (ask_pipeworx, compare_entities), some are single words (forget, recall, remember), and others are noun-based (compliance_catalog, entity_profile). No consistent pattern.

Tool Count1/5

With 34 tools, the count is too high for a server named 'ISO Standards'. The majority of tools are unrelated to ISO standards (e.g., Polymarket, memory, web scraping), making the scope highly inappropriate.

Completeness1/5

As an ISO standards server, the tool set is severely incomplete. Only 4-5 tools (search_standards, get_standard, compliance_catalog, open_data_files) actually deal with ISO standards. Essential operations like comparing standards or browsing revisions are missing.

Resources