TENEKS MCP

Ask about TENEKS recordings

ask_teneks

Read-onlyIdempotent

Ask a question across the user's recordings and get a grounded answer.

Use this for questions that span many calls -- patterns, comparisons,
recurring objections, how a rep is doing. For one specific call, prefer
get_transcript, which returns what was said rather than an interpretation.

The answer is computed from the user's own recordings and is scoped to what
they are allowed to see. Check `status`: `incomplete` means the answer could
not be fully grounded in the underlying calls, or the analysis ran out of
time, and it should not be repeated as fact.

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": {
      "question": "<question>"
    },
    "name": "ask_teneks"
  }
}

Input Schema

Name	Required	Description	Default
`question`	Yes	A question about this user's calls, in any language. e.g. 'what objections came up most last month?'

Output Schema

Name	Required	Description
`notes`	No
`answer`	Yes
`intent`	No	How the question was interpreted.
`status`	Yes	complete, or incomplete when the answer could not be fully grounded or the request ran out of time. Do not present an incomplete answer as a finding.
`time_range`	No	The period actually analysed, which may be wider than asked.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare read-only and idempotent behavior, so the safety profile is covered. The description adds meaningful context beyond annotations: the answer is computed from the user's own recordings, scoped to their permissions, and the `status` field can be `incomplete` when grounding fails or analysis times out. That extra caveat is important behavioral context.

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 description is front-loaded with the core action, then usage guidance, then behavioral caveats. It is reasonably compact, though the final status warning is somewhat detailed and could be slightly tighter.

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 one-parameter read-only query tool with an output schema, the description covers the essential context: scope, alternative tool, permission-bound results, and the meaning of incomplete status. Nothing critical is missing for correct invocation.

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?

There is only one parameter, and the schema has 100% coverage with an example question. The description reinforces that questions span recordings, but it does not add format, syntax, or constraint details beyond what the schema already provides.

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 states a specific verb and resource: ask a question across the user's recordings and get a grounded answer. It also explicitly distinguishes itself from get_transcript, making the tool's role clear among its siblings.

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?

It gives explicit when-to-use guidance for cross-call questions such as patterns, comparisons, recurring objections, and rep performance. It also names the alternative for a single call, get_transcript, and explains the selection criterion.

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

All TENEKS MCP tools Inspect

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

Need Help?