Skip to main content
Glama

Dante IX — Brand & GEO Intelligence

Query Customer Friction & Social Signal Vault

dante.query_street_friction
Read-onlyIdempotent

Search the caller's isolated tenant signal vault for customer complaints, sarcasm/irony-calibrated sentiment records, coordinated bot anomaly alerts, and unmet competitor gaps. Returns a JSON object (query, voice_filter, matched_count, records, and tier_mode). Side effects & latency: Strictly read-only (readOnlyHint=true), deterministic, and zero external LLM cost; executes in <200ms against the isolated tenant index. Never accesses or leaks signals belonging to other tenants. Auth & quota: Consumes 0 live audit credits. Without DANTE_API_KEY, searches the isolated free-trial sandbox vault and returns a 30% preview; with a paid dnt_live_ key, searches the caller's dedicated private tenant vault and returns full records. When to use: Use dante.query_street_friction to inspect specific recurring customer pain points (e.g. 'pricing OR billing OR delay') after running dante.run_audit. Do not use this tool to query live external LLMs (use dante.probe_geo_share instead) or to generate website schema files (use dante.forge_geo_shield instead).

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": {
      "query": "<query>"
    },
    "name": "dante.query_street_friction"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of matching signal records to return (integer between 1 and 100, defaults to 10).
queryYesSearch keywords or boolean expression to match against indexed social and customer signals (2 to 240 chars, e.g. 'pricing OR support OR latency').
voice_filterNoFilter records by source voice category: 'ALL' (every source), 'OWN_VOICE' (official brand channels), 'ALLY_ADVERSARY_VOICE' (competitors/press/affiliates), or 'SECTOR_STREET_VOICE' (organic customers).ALL

Output Schema

NameRequiredDescriptionDefault
queryNoExecuted search query string.
recordsNoList of attested customer signal records with sentiment and bot-risk flags.
tier_modeNoActive license tier.
voice_filterNoApplied voice category filter.
matched_countNoNumber of matching records returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum records to return (1 to 100)"New value: +"Maximum number of matching signal records to return (integer between 1 and 100, defaults to 10)."
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / query / description
      Previous value: -"Search keywords (e.g. 'pricing OR support OR latency')"New value: +"Search keywords or boolean expression to match against indexed social and customer signals (2 to 240 chars, e.g. 'pricing OR support OR latency')."
    • addedInput schema / properties / query / maxLength
      Added value: +240
    • addedInput schema / properties / query / minLength
      Added value: +2
    • changedInput schema / properties / voice_filter / description
      Previous value: -"Voice filter: 'ALL', 'OWN_VOICE', 'ALLY_ADVERSARY_VOICE', or 'SECTOR_STREET_VOICE'"New value: +"Filter records by source voice category: 'ALL' (every source), 'OWN_VOICE' (official brand channels), 'ALLY_ADVERSARY_VOICE' (competitors/press/affiliates), or 'SECTOR_STREET_VOICE' (organic customers)."
    • addedInput schema / properties / voice_filter / enum
      Added value: +[
      +  "ALL",
      +  "OWN_VOICE",
      +  "ALLY_ADVERSARY_VOICE",
      +  "SECTOR_STREET_VOICE"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "matched_count": {
      +      "description": "Number of matching records returned.",
      +      "type": "integer"
      +    },
      +    "query": {
      +      "description": "Executed search query string.",
      +      "type": "string"
      +    },
      +    "records": {
      +      "description": "List of attested customer signal records with sentiment and bot-risk flags.",
      +      "type": "array"
      +    },
      +    "tier_mode": {
      +      "description": "Active license tier.",
      +      "type": "string"
      +    },
      +    "voice_filter": {
      +      "description": "Applied voice category filter.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile, but the description goes well beyond them: sub-200ms latency, determinism, zero external LLM cost, zero audit-credit consumption, and explicit tenant isolation ('never accesses or leaks signals belonging to other tenants'). Critically, it discloses the credential-dependent behavior — without DANTE_API_KEY a free-trial sandbox returns a 30% preview, while a dnt_live_ key returns full records — which materially changes how an agent should interpret matched_count and result completeness.

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?

Long but deliberately segmented into labelled blocks (Returns, Side effects & latency, Auth & quota, When to use) that let an agent jump to the relevant clause. Every sentence carries routing, safety, or quota information with no filler.

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 a 3-parameter read tool this covers the decision-relevant surface: scope, cost, latency, tenant isolation, and the credential tier that determines result completeness. The only slack is that it enumerates return fields (`query`, `voice_filter`, `matched_count`, `records`, `tier_mode`) that an output schema already declares, which is mild duplication rather than an information gap.

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 100% and the schema already documents all three parameters including the voice_filter enum values and limit bounds, so the description need not compensate. The description adds only a runnable boolean query example ('pricing OR billing OR delay'); it says nothing about how voice_filter or limit affect results, so it earns baseline rather than above it.

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 first sentence names a specific verb (search) and a precisely scoped resource (the caller's isolated tenant signal vault) and enumerates the record types returned (complaints, calibrated sentiment, bot alerts, competitor gaps). It also explicitly excludes sibling responsibilities, so an agent can distinguish it from dante.probe_geo_share and dante.forge_geo_shield without opening either schema.

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?

Provides an explicit 'When to use' trigger (inspecting recurring pain points after running dante.run_audit) and a 'Do not use' clause that names the two alternative tools for the excluded cases. Both the positive and negative routing conditions are stated, leaving nothing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources