Skip to main content
Glama

Veyrul media knowledge hub

Search media knowledge

search
Read-only

Find evidence before choosing a media workflow, diagnosing a failed result or comparing creative/technical approaches. Search model/version plus the constraint; inspect matching records with get_record before applying them. Non-guide public reads and approved previews need no account; full guides use the versioned registered-agent boundary described in the server instructions. Searches cover: discussions (questions, answers, findings), projects, sources, workflows, prompts, experiments, evaluations, assets and articles. Filters: types, categories (no license/level filter; such arguments are refused). Hits: id, type, title, status, evidence (inspection/execution/review), snippet, url.

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": {
      "q": "<q>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesNonconfidential media task or search terms, including relevant model/version and constraints.
limitNoMaximum number of results within the documented per-tool range.
typesNoOptional allowed record types. Omit to search all supported knowledge types.
cursorNoOpaque next_cursor returned by the same search/listing. Omit for the first page.
categoriesNoOptional media category IDs from the service capability manifest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / categories / description
      Added value: +"Optional media category IDs from the service capability manifest."
    • addedInput schema / properties / cursor / description
      Added value: +"Opaque next_cursor returned by the same search/listing. Omit for the first page."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of results within the documented per-tool range."
    • addedInput schema / properties / q / description
      Added value: +"Nonconfidential media task or search terms, including relevant model/version and constraints."
    • addedInput schema / properties / types / description
      Added value: +"Optional allowed record types. Omit to search all supported knowledge types."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond the readOnly/openWorld/destructive annotations: the auth boundary (public reads and previews need no account, full guides require a versioned registered-agent boundary), an explicit refusal rule (license/level filters are refused), and the shape of returned hits. With no output schema present, spelling out the hit fields is real added value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose and the follow-up action, then packs scope, filters, and hit shape into short clauses with no filler. It is dense to the point of being terse—several distinct concerns crammed into four sentences—but every sentence carries information.

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?

Covers purpose, auth prerequisites, filtering constraints, and return fields for a read-only search with no output schema, which is most of what an agent needs. The registered-agent boundary is delegated to 'server instructions' rather than described, leaving one prerequisite underspecified.

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 baseline is 3, but the description adds meaning the schema does not: it tells the agent to put model/version and the constraint into the query, and that category filtering deliberately excludes license/level arguments which will be refused. Those are semantic constraints beyond the field docs.

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 ('Find evidence', searches across discussions, projects, sources, workflows, prompts, experiments, evaluations, assets, articles) and names the sibling it hands off to ('inspect matching records with get_record'). An agent can distinguish it from get_record and the other listing tools without opening any schema.

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?

Gives concrete when-to-use triggers (before choosing a workflow, diagnosing a failed result, comparing approaches) and an explicit sequel ('inspect matching records with get_record before applying them'). It lacks an explicit when-not-to-use statement or a named alternative for record lookup, so it stops short of the top band.

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