Temsor API — Turkey & EU business data

PBX Register

pbx_register

Control-plane register. API key shown once; stored hashed at rest. Send x-temsor-pbx-key to scope GET /v1/pbx/promises to this pbx_id. No speech recognition while idle.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Pilot contact name (waitlist / register).
`email`	No	Pilot contact email.
`label`	No	Human label, e.g. hotel or PBX/IT provider site.
`pbx_id`	No	Pilot PBX id; auto-minted if omitted.
`webhook_url`	No	Optional outbound webhook URL — Temsor POSTs promise/fact/orchestra/redact events.
`webhook_events`	No	Event list or comma string: promise.opened\|closed, fact.extracted, orchestra.act, redact, or *.
`webhook_secret`	No	Optional HMAC secret for outbound webhook signatures (x-temsor-signature).
`ari_webhook_secret`	No	ARI webhook signing secret (stored as hint only).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 9, 2026

addedInput schema / properties / webhook_events

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "string"
+    }
+  ],
+  "description": "Event list or comma string: promise.opened|closed, fact.extracted, orchestra.act, redact, or *."
+}

addedInput schema / properties / webhook_secret

Added value: +{
+  "description": "Optional HMAC secret for outbound webhook signatures (x-temsor-signature).",
+  "maxLength": 200,
+  "type": "string"
+}

addedInput schema / properties / webhook_url

Added value: +{
+  "description": "Optional outbound webhook URL — Temsor POSTs promise/fact/orchestra/redact events.",
+  "format": "uri",
+  "maxLength": 500,
+  "type": "string"
+}

Changed2 schema fields changedSep 8, 2026

changedInput schema / properties / label / description

Previous value: -"Human label, e.g. hotel or MSP site."New value: +"Human label, e.g. hotel or PBX/IT provider site."

changedInput schema / properties / name / description

Previous value: -"Pilot contact name (waitlist / register stub)."New value: +"Pilot contact name (waitlist / register)."

Changed4 schema fields changedSep 8, 2026

addedInput schema / properties / email

Added value: +{
+  "description": "Pilot contact email.",
+  "format": "email",
+  "maxLength": 254,
+  "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
+  "type": "string"
+}

addedInput schema / properties / name

Added value: +{
+  "description": "Pilot contact name (waitlist / register stub).",
+  "maxLength": 120,
+  "type": "string"
+}

changedInput schema / properties / pbx_id / description

Previous value: -"Pilot PBX id (customer Asterisk / FreePBX)."New value: +"Pilot PBX id; auto-minted if omitted."

removedInput schema / required
```
Removed value: -[
-  "pbx_id"
-]
```

AddedSep 8, 2026

TDQS

A4.2/5.0

Behavior5/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, and it delivers: API key shown once and hashed at rest, a rate limit with the exact 429 consequence, idle pricing, the x-temsor-pbx-key scoping mechanism, and the idle speech-recognition limitation. This goes well beyond a simple 'register' claim.

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

Conciseness3/5

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

The text is short and front-loaded, but it repeats itself: 'API key shown once; stored hashed at rest' appears in both the first sentence and the second paragraph. Some extra behavior like 'No speech recognition while idle' is relevant, yet the duplication makes the description slightly less efficient than it could be.

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

Completeness4/5

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

For an 8-parameter registration tool with no annotations and no output schema, the description covers the essential behavioral context: return value, security handling, rate limit, cost, and API-key usage. Minor gaps remain, such as the exact response format and any prerequisites, but an agent has enough to invoke it correctly.

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 description coverage is 100%, so the structured parameters already fully document fields like name, email, pbx_id, and webhook settings. The description does not add parameter-specific guidance, but it doesn't need to because the baseline 3 applies when the schema does the heavy lifting.

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 opens with a specific verb and resource: 'Register a pilot PBX', immediately identifying the action and target. It also states the key result (returns pbx_id + API key) and clarifies this is a control-plane operation, distinguishing it from the many other pbx_* siblings, none of which are a registration tool.

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?

The description gives clear context: rate limit of ≤5/hour/IP with 429, idle cost of $0, and a note that speech recognition is unavailable while idle. It doesn't explicitly name alternatives or when-not conditions, but the tool name and purpose make it obvious this is the registration entry point, so no exclusion is needed.

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?