Skip to main content
Glama

Agentic Endpoints

by com.oliverkiss

Search your meeting transcripts

meetings_search
Read-onlyIdempotent

Ask a question across every meeting you have imported as queryable, and get back ranked excerpts with the meeting they came from. This is the tool to use when the user refers to something that was said, agreed, or decided in a call -- 'what did we decide about pricing', 'who owned the migration', 'when did we say we would ship'. Returns 'searched_meetings' and 'private_meetings_skipped': meetings imported as private are encrypted and CANNOT be searched, so if searched_meetings is 0 an empty result means nothing was searched, NOT that the topic was never discussed. Use meetings_get to read a full transcript once you have found the right meeting. Costs $0.006 in USDC on Base, paid via the x402 protocol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results, 1-50 (default 10)
queryYesFTS5 match expression. Use quotes for phrases, e.g. "budget review". Prefer a few distinctive words over a whole sentence.
namespaceYesIsolation scope holding your meetings
namespace_tokenYesOne-time token issued by the first call that claimed this namespace. Required for every later call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of matches returned
queryNoThe match expression that was run
statusYes'ok' on a successful search
matchesYesRanked excerpts, best first
searched_meetingsNoHow many meetings were actually searched. If 0, an empty result means nothing was searchable, NOT that the topic was never discussed.
private_meetings_skippedNoEncrypted meetings that could not be searched

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark this readOnly and idempotent, and the description goes well beyond them by disclosing return fields (searched_meetings, private_meetings_skipped), the privacy/encryption limitation, the meaning of a zero search count, and the per-call cost via x402. No contradiction with annotations.

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?

Although slightly longer than average, every sentence earns its place: the core purpose is front-loaded, followed by usage examples, the critical private-meeting caveat, a routing pointer, and cost. There is no fluff or repetition of schema content.

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 search tool with four parameters, an output schema, and rich annotations, the description is complete. It covers behavior, edge cases, follow-up routing, and cost. Nothing an agent needs to invoke it correctly appears to be 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?

Input schema covers 100% of the parameters, so the baseline is 3. The description adds real value by explaining the query parameter's FTS5 behavior, recommending quoted phrases, and advising distinctive keywords over full sentences, which helps the agent construct better queries.

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?

The description clearly identifies the tool as semantic search over imported meeting transcripts, with the specific verb 'Ask a question' and resource 'every meeting you have imported as queryable'. It distinguishes itself by positioning against meetings_get: use this to find the right excerpt, then use meetings_get to read the full transcript.

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?

Explicitly states when to use: when the user refers to something said, agreed, or decided in a call, with concrete example queries. It also gives an important exclusion: private meetings are encrypted and cannot be searched, and explains the empty-result caveat. It routes to the correct sibling for follow-up reading of full transcripts.

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

All Agentic Endpoints toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool maps to a distinct resource and action: meetings have import/list/search/get, the once-key system has claim/complete/release, vault has store/retrieve/exists/list/delete/rotate_token, and compress/pdf_parse/scrape are separate utilities. No two tools appear to perform the same side effect, so an agent should not struggle to choose among them.

Naming Consistency5/5

Tools use consistent snake_case and mostly follow a domain_verb pattern (meetings_*, once_key_*, vault_*), with standalone verbs like compress, scrape, and pdf_parse for single utilities. The naming is predictable and easy to extend.

Tool Count4/5

At 16 tools the server is just above the ideal 3-15 range, but the count is justified by six distinct capability clusters. Each tool earns its place, and nothing feels redundant.

Completeness4/5

Core lifecycles are covered well: vault has full CRUD plus token rotation, once-key has claim/complete/release, and meetings provide import/search/get/list. Minor gaps include no meeting update/delete and no direct namespace management, but these are workable rather than blocking.

Resources