Skip to main content
Glama

Temsor API — Turkey & EU business data

by com.temsor
OverviewDiscussionsAdmin

PBX Dictionary Add Alias

pbx_dictionary_add

Add a synonym/alias (tenant-scoped or global demo) — E4 compounding thickens search boost + Fact extract. ≤60/hour/key → 429. Idle $0. No invented premiums.

POST /v1/pbx/dictionary/add {term, alias, domain:otel|santral_firmasi|sigorta|finans|enerji|otomotiv, scope?:pbx|global}. Managed SaaS compounding (E4): tenant-scoped aliases thicken search + fact extract. No invented premiums/prices. Idle $0, no LLM. Legacy msp → santral_firmasi.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoFact kind; inferred from seed term when omitted.
termYesCanonical term (e.g. AC, tariff). Plain Turkish preferred.
aliasYesSynonym / alias to add (e.g. cooling, line package).
boostNoSearch boost weight (default 2).
scopeNopbx = scoped to x-temsor-pbx-key; global = demo-wide. Default: pbx if registered key, else global.
domainNoDomain: otel | santral_firmasi | sigorta | finans | enerji | otomotiv (legacy msp accepted).otel
hint_enNo
hint_trNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"Domain: otel | santral_firmasi | sigorta | finans | enerji (legacy msp accepted)."New value: +"Domain: otel | santral_firmasi | sigorta | finans | enerji | otomotiv (legacy msp accepted)."
    • changedInput schema / properties / domain / enum
      Previous value: -[
-  "otel",
-  "santral_firmasi",
-  "msp",
-  "sigorta",
-  "finans",
-  "enerji"
-]New value: +[
+  "otel",
+  "santral_firmasi",
+  "msp",
+  "sigorta",
+  "finans",
+  "enerji",
+  "otomotiv"
+]
  2. Changed3 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"Domain: otel | santral_firmasi (legacy msp accepted)."New value: +"Domain: otel | santral_firmasi | sigorta | finans | enerji (legacy msp accepted)."
    • changedInput schema / properties / domain / enum
      Previous value: -[
-  "otel",
-  "santral_firmasi",
-  "msp"
-]New value: +[
+  "otel",
+  "santral_firmasi",
+  "msp",
+  "sigorta",
+  "finans",
+  "enerji"
+]
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "imei",
-  "tarife",
-  "oda",
-  "oda_tipi",
-  "klima",
-  "check_out",
-  "iade",
-  "sku",
-  "other"
-]New value: +[
+  "imei",
+  "tarife",
+  "oda",
+  "oda_tipi",
+  "klima",
+  "check_out",
+  "iade",
+  "sku",
+  "police",
+  "hasar",
+  "yenileme",
+  "abone",
+  "kesinti",
+  "fatura",
+  "kart",
+  "iban",
+  "sube",
+  "other"
+]
  3. Added

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose real traits: a rate limit of 60/hour/key returning 429, idle cost of $0, no LLM involvement, and scope resolution based on whether an x-temsor-pbx-key is registered. However, it omits what happens on duplicate/conflicting aliases, whether adds are reversible, and the auth requirement itself is only implied.

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?

Two paragraphs with heavy repetition — the endpoint and the E4/compounding/'no invented premiums' phrasing appear twice, and 'Managed SaaS compounding (E4): tenant-scoped aliases thicken search + fact extract' duplicates the first sentence. Marketing language crowds out the operational facts.

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?

For an 8-parameter mutation tool with no output schema and no annotations, the description covers rate limits, scope resolution, domain legacy mapping, and cost, which is more than minimal. But it is silent on response shape, duplicate handling, and error behavior beyond the 429, leaving gaps for a write operation.

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 75%, so the schema already documents most parameters, making 3 the baseline. The description mostly restates the enum values the schema already carries and is even narrower for domain (omits msp), adding little new meaning beyond the schema's own descriptions.

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 opening states a specific verb and resource ('Add a synonym/alias') and scopes it ('tenant-scoped or global demo'), so an agent can identify the operation. It does not explicitly differentiate itself from the sibling pbx_dictionary (presumably the read counterpart), and the marketing noise around it dilutes the signal, but the core 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?

No statement of when to use this versus pbx_dictionary, pbx_search, or pbx_facts. Usage is only inferable from the tool name. The description gives conditions like rate limits but never says 'use this when you need to register a new alias'.

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 toolsInspect
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