Skip to main content
Glama

Ask the talks archive a question (public)

ic_presentations_ask
Read-only

Searches every Immersive Commons talk by meaning and returns the matching slides, the same as the search box on /presentations: talk title, series, speaker, the slide number, a snippet, a deep link straight to that slide in the public deck, and the talk's page. Retrieval only, no generated answer: read the snippets and follow deep_link. At most 3 hits per talk. No auth required. Budget: 40 questions per hour per token, and one shared hourly budget for all anonymous agents, so pass a token if you have one. Args: { q: string (1-500 chars), k?: integer 3-25 (default 10) }. Returns { ok, q, count, results: [{ slug, talk_title, series, speaker, similarity, slide, snippet, deep_link, detail_link }], via }.

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

Input Schema

NameRequiredDescriptionDefault
kNoHow many slides to return, 3-25. Default 10.
qYesWhat you want to find in the talks, in plain words, e.g. "how do agents pay each other".

Output Schema

NameRequiredDescriptionDefault
okNotrue when the call did what it was asked; false with `error` and `error_kind` when it did not
textNoThe tool's reply when it returns plain text instead of JSON
errorNoWhy the call failed, in a sentence a person can act on. Present only when ok is false.
resultNoThe tool's value when it returns a list or a single value instead of an object
error_kindNoMachine-readable failure class: no_token, missing_scope, forbidden, not_found, invalid_input, rate_limited or transient

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "description": "The tool's JSON result. Every field the tool's description names is present at the top level; ok, error and error_kind follow the shared envelope.",
      +  "properties": {
      +    "error": {
      +      "description": "Why the call failed, in a sentence a person can act on. Present only when ok is false."
      +    },
      +    "error_kind": {
      +      "description": "Machine-readable failure class: no_token, missing_scope, forbidden, not_found, invalid_input, rate_limited or transient"
      +    },
      +    "ok": {
      +      "description": "true when the call did what it was asked; false with `error` and `error_kind` when it did not"
      +    },
      +    "result": {
      +      "description": "The tool's value when it returns a list or a single value instead of an object"
      +    },
      +    "text": {
      +      "description": "The tool's reply when it returns plain text instead of JSON"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses no-auth operation, two distinct rate limits (40 questions/hour per token plus a shared anonymous budget), a per-talk cap of 3 hits, and the crucial retrieval-only/no-generation behavior. These are exactly the operational traits an agent needs and none are recoverable from 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.

Conciseness4/5

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

The opening sentence front-loads the core purpose, and the ordering (what it does, limits, auth, budget, args, returns) is logical. It is somewhat packed into one dense paragraph, and the explicit 'Returns {...}' enumeration largely duplicates the existing output schema, costing a bit of efficiency.

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?

For a two-parameter read-only search with an output schema, the definition covers everything an agent needs: semantics of retrieval, per-talk limits, auth, rate budgets, and where to look in the response. Nothing material is left to guesswork.

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?

With 100% schema description coverage, the schema already documents both q and k including the 3-25 range and default. The description's 'Args: { q: string (1-500 chars), k?: integer 3-25 (default 10) }' restates the schema rather than adding new meaning, so baseline 3 applies.

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 and resource ('Searches every Immersive Commons talk by meaning and returns the matching slides') plus a concrete analogy to the /presentations search box, so the agent knows exactly what it does. It does not explicitly contrast itself with the sibling retrieval tools (ic_presentations_list, ic_presentations_get), so a 4 rather than 5.

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?

Strong usage cues are present: 'Retrieval only, no generated answer: read the snippets and follow deep_link' tells the agent both what to expect and what to do with the output, and 'pass a token if you have one' directs token usage under the shared budget. No explicit when-not-to-use or named alternative among siblings, keeping it at 4.

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.