Skip to main content
Glama
Sign In

Veyrul media knowledge hub

by com.veyrul
OverviewDiscussionsAdmin

Reuse media knowledge and resources

get_context
Read-only

Use as the first focused lookup when choosing a media workflow, finding reusable code or references, or diagnosing a production problem. Start with detail=compact and limit=3; skip unrelated work and simple already-supported facts. Returns saved findings, prompts, workflows and author-linked examples together, including hosted file downloads and external footage/repository/resource locations. Query with the technique, subject, model or constraint. Use detail=compact for up to 5 matching records plus 3 related records, with 4,000 body characters per record and a 64 KiB response ceiling. detail=full (also the compatibility default) allows 6 related records and 12,000 body characters. Evidence, rights and resource locations remain included; follow content_truncated records for full detail. If a broad question misses a requested resource, try up to two focused searches for its subject/model and resource kind, using types when useful; one missed query does not establish absence. Reuse supported knowledge; research remaining gaps or stale claims only. External links do not imply free access, a download or reuse rights. Anonymous non-guide references and separately approved previews; full guides require catalog2.0 and current agent/review authorization. No media generation or external downloads.

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

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.
detailNocompact returns bounded saved content and resources; full includes more related content.
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 / detail / description
      Added value: +"compact returns bounded saved content and resources; full includes more related content."
    • 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. Changed1 schema field changed
    • addedInput schema / properties / detail
      Added value: +{
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, not open-world), and the description layers on substantial extra context: concrete response ceilings (64 KiB), per-record body caps (4,000 vs 12,000 characters), related-record counts, truncation handling via content_truncated, and access-tiering rules for guides/previews. It also warns that external links imply no free access or reuse rights — genuinely useful behavioral context beyond structured fields.

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?

The text is front-loaded with the use case and starting parameters, then moves to return shape, failure recovery, and access caveats in a logical order, and nearly every sentence carries operational content. It is dense and slightly repetitive around detail modes and access restrictions, which keeps it off a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates fully: it describes what comes back (findings, prompts, workflows, examples, resource locations), the size limits, the truncation signal, and the authorization requirements for restricted content. For a five-parameter read tool with annotations already declaring safety, nothing an agent needs to call it correctly is missing.

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 real meaning by contrasting compact (5 matches + 3 related, 4,000 chars, 64 KiB cap) against full (6 related, 12,000 chars) and by framing q as technique/subject/model/constraint terms and types as an optional narrowing facet. That is decision-relevant trade-off information the enum strings alone do not convey.

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 states a specific verb-plus-resource: a focused lookup over saved media knowledge (findings, prompts, workflows, author-linked examples) with hosted files and external resource locations. It clearly bounds scope with 'No media generation or external downloads.' It stops short of naming a sibling alternative for the same intent, so differentiation is by scope only rather than by routing.

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?

Explicit when-to-use triggers are given ('first focused lookup when choosing a media workflow, finding reusable code or references, or diagnosing a production problem') along with when-not ('skip unrelated work and simple already-supported facts'). It also prescribes an operating procedure (start with detail=compact and limit=3; up to two focused follow-up searches when a resource is missed) and a stopping rule ('one missed query does not establish absence').

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

All Veyrul media knowledge hub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources