Skip to main content
Glama

Search Populi API routes

populi_search_api
Read-onlyIdempotent

Search the Populi API v2 route catalog by keyword or exact route ID to find an endpoint's method and path before describing its parameters.

Instructions

Search the Populi API v2 route catalog (697 routes across 180 models) by keyword, e.g. 'application', 'enrollments', 'invoice', 'course offering'. Returns route ids with method and path. Use this first to find the right route, then populi_describe_api for its parameters.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum routes to return
queryYesKeywords, or an exact route id like people.create
methodNoOnly routes with this HTTP method

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.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 observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description adds meaningful context beyond them: the size of the catalog being searched, that results are route ids with method and path, and that matching accepts keywords or an exact route id. It stops short of describing ranking or no-match behavior, so it is strong but not exhaustive.

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 short sentences, front-loaded with what is searched and what comes back, then the routing advice. Every sentence carries distinct information with no redundant restatement of the schema or title.

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?

No output schema exists, and the description compensates by stating the return payload. All three parameters are fully documented in the schema, so the remaining need is low. A note on result truncation or no-match handling would close the last gap.

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%, so the schema already documents query, limit, and method. The description still contributes value by illustrating the query parameter's intended granularity (keyword examples like 'course offering' versus an exact route id such as people.create), which clarifies matching behavior the schema does not spell out.

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?

States a specific verb and resource (search the Populi API v2 route catalog) with scale (697 routes across 180 models) and return shape (route ids with method and path), plus concrete keyword examples. It is clearly distinguishable from populi_describe_api, which it explicitly defers detail lookup to.

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

Usage Guidelines5/5

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

Gives an explicit workflow: 'Use this first to find the right route, then populi_describe_api for its parameters.' The sequencing and the alternative for the next step are both named, leaving no inference required about when to reach for this tool.

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