Temsor API — Turkey & EU business data

Voice Archive Search

pbx_search

Agent archive search over call promises and facts — voice-Google for call-ops, not a receptionist bot. Idle $0.

Demo index + domain dictionary v0. Filters: status, date, ext, competitor, stuck_after (transfer/handoff hop). Returns call-graph path + transfer edges for orchestration. Idle $0. No live PSTN.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Full-text query over promises, facts, and call summaries.
`ext`	No
`status`	No
`date_to`	No	ISO date/time upper bound.
`date_from`	No	ISO date/time lower bound (promise.when_iso / call.started_at).
`competitor`	No
`stuck_after`	No	Filter: promise stuck after transfer to this extension (to_ext hop).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 9, 2026

addedInput schema / properties / stuck_after

Added value: +{
+  "description": "Filter: promise stuck after transfer to this extension (to_ext hop).",
+  "maxLength": 16,
+  "type": "string"
+}

Changed3 schema fields changedSep 8, 2026

addedInput schema / properties / date_from

Added value: +{
+  "description": "ISO date/time lower bound (promise.when_iso / call.started_at).",
+  "maxLength": 40,
+  "type": "string"
+}

addedInput schema / properties / date_to

Added value: +{
+  "description": "ISO date/time upper bound.",
+  "maxLength": 40,
+  "type": "string"
+}

changedInput schema / properties / q / description

Previous value: -"Full-text query over promises and call summaries."New value: +"Full-text query over promises, facts, and call summaries."

AddedSep 8, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses important traits: it is a 'Demo index' (limited data), 'Idle $0' (cost-free), and 'No live PSTN' (no live telephony access). It also states the output shape ('call-graph path + transfer edges'). However, it does not cover potential limitations like pagination, auth requirements, or data freshness beyond 'demo'.

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

Conciseness2/5

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

The description is short but contains redundancy: 'Idle $0' appears twice. The structure jumps from purpose to analogy to filters to returns without a clear hierarchy. The informal phrasing ('voice-Google for call-ops') adds flavor but not clarity. While not overly verbose, the repetition and lack of front-loading of essential constraints hurt conciseness.

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

Completeness3/5

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

With no output schema, the description does explain the return type ('call-graph path + transfer edges'), which is essential. It also notes the demo nature and non-live status. However, it does not mention result limits, pagination, or how filters combine. Given the complexity of a full-text search over promises and facts, more details about expected output structure or result size would improve completeness.

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?

Schema coverage is 57%, leaving ext, status, and competitor without descriptions. The description lists these as filters but adds no meaning beyond the names. It does add a clarifying note for stuck_after ('transfer/handoff hop'), which is useful. For a moderate coverage level, the description partially compensates but does not fully explain the undocumented parameters.

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 clearly states the core action: 'Agent archive search over call promises and facts' – a specific verb (search) over a defined resource (archive of promises and facts). It adds an analogy ('voice-Google for call-ops') and a negative ('not a receptionist bot') that convey intended usage. It does not explicitly differentiate from sibling tools like pbx_calls or pbx_facts, but the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description lists filters and states the return type ('call-graph path + transfer edges for orchestration'), implying it is for agent-side orchestration. However, it never explicitly says when to use this tool versus the many pbx_* siblings (e.g., pbx_calls, pbx_facts_get). No alternatives or exclusion criteria are mentioned, so guidance is implied at best.

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

All Temsor API — Turkey & EU business data 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?