Skip to main content
Glama
simap MCP Server

simap MCP Server

by Digilac

Search OAG Codes

search_oag_codes
Read-onlyIdempotent

Search OAG object type classification codes by keyword or code number to identify correct classifications for Swiss public tenders.

Instructions

Search OAG (object type classification) codes by keyword or 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": {
      "query": "<query>"
    },
    "name": "search_oag_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoSearch languageen
queryYesSearch term (keyword or code number)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv1.3.0

TDQS

B3.1/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds almost no behavioral context beyond that, such as matching semantics, result limits, or how language affects search.

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 a single front-loaded sentence with no wasted wording. It delivers the core purpose and acronym expansion efficiently.

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?

For a simple two-parameter search tool with rich annotations and no output schema, the description is minimally adequate. However, given several similarly named sibling search tools and a browse_oag_tree alternative, it lacks the differentiation needed for reliably selecting this 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 description coverage is 100%, so both the query and lang parameters are already documented in the schema. The description's phrase 'keyword or number' largely restates the schema's own query description and adds no syntax or format guidance.

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 ('Search') and resource ('OAG codes') and expands the unfamiliar OAG acronym as object type classification. It is clear what the tool does, but it does not distinguish itself from sibling code-search tools such as search_cpv_codes, search_bkp_codes, or search_npk_codes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies searching by keyword or number but provides no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as browse_oag_tree. With multiple near-identical sibling search tools, this leaves routing entirely to inference.

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