Skip to main content
Glama

detect_intent

Sends user text to a Dialogflow CX agent and returns the reply, matched intent, active page, and extracted parameters; reuse the session ID to maintain conversation context.

Instructions

Send a user message to the Dialogflow CX agent and return the agent's reply, matched intent, active page, and extracted parameters. Pass the returned session_id back on subsequent calls to maintain conversational context.

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": {
      "text": "<text>"
    },
    "name": "detect_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
session_idNo
language_codeNoen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it does disclose the return payload and the stateful session behavior, which is real value beyond structured fields. It does not disclose that intent detection can trigger agent fulfillment/webhooks (side effects), nor error behavior for unmatched input, auth requirements, or latency/rate limits.

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?

Two sentences, action front-loaded, followed by the stateful-usage note. Every clause earns its place, with no restating of the tool name or filler.

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?

There is no output schema, and the description does a reasonable job listing the response fields, so return values are largely covered. However, an undocumented language_code parameter and the absence of any note about side effects or failure modes leave gaps for a conversational agent call.

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 0%, so the description must compensate. It gives clear meaning for text (the user message) and session_id (context continuity), but language_code—which defaults to "en"—is never mentioned, so one of three parameters is left entirely to the schema title.

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?

States a concrete verb+resource ("Send a user message to the Dialogflow CX agent") and enumerates what comes back: reply, matched intent, active page, extracted parameters. There are no siblings to differentiate against, but the action is unambiguous without opening the schema.

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

Usage Guidelines3/5

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

The only usage guidance is the multi-turn hint—pass session_id back on subsequent calls to maintain context—which is genuinely useful. It says nothing about prerequisites (a configured agent, credentials), when not to call it, or how to start a fresh conversation by omitting session_id.

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

Deploy Server

Other Tools