Skip to main content
Glama

Agent Help Network

find_task_route

Read-onlyIdempotent

Call this once per task when you start a customer task on a site (a return or exchange, a refund, a cancellation, a warranty claim, an account recovery, a document submission), before you open its help pages, even when nothing is blocked. Look up recorded task routes for a public hostname: for a kind of customer task (a refund, a cancellation, a booking and so on), an obstacle and the routes the site's own documents name. A record may carry condition_text, a condition the site's page states, quoted as written: it is not our judgement, so decide yourself whether it applies to your task, with the page at source_url. The answer is a list of records, not a guarantee and not advice; an empty list does not mean there is no route. Sends only the hostname and an optional task kind, and changes nothing. Read summary_line first. field_notes explains outcome, period and routes_tried.

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": {
      "site_host": "<site_host>"
    },
    "name": "find_task_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_hostYesThe public hostname of the site whose task routes you want, lowercase, for example example.com. Only the host: no scheme, URL path, query, port or credentials.
task_kindNoOptional: one kind of customer task to look up, from the list. Leave it out to get the records for every task kind of the site.

Output Schema

NameRequiredDescriptionDefault
countsYes
noticeNo
routesNo
site_hostYes
field_notesNoFixed sentences on what outcome, period and routes_tried mean in these records (those keys are left out when there is no record), and call_timing, when to call this lookup (always present).
summary_lineYes
official_help_urlNoOnly when routes is empty and the site's own help or customer service page is curated: that page, as a place to look yourself. A link to read, not a route and not a statement that the site has none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / $defs / TaskRoute / properties / condition_text / anyOf
      Previous value: -[
      -  {
      -    "maxLength": 200,
      -    "minLength": 1,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maxLength": 280,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / $defs / TaskRoute / properties / condition_text / description
      Previous value: -"A condition or caveat quoted as the site's own page words it (at most 200 characters). Not our judgement and not classified: whether it applies to your task is for you to decide, with the page at source_url. It may state a condition other than the obstacle."New value: +"A condition or caveat quoted as the site's own page words it (at most 280 characters). Not our judgement and not classified: whether it applies to your task is for you to decide, with the page at source_url. It may state a condition other than the obstacle."
  2. Changed3 schema fields changed
    • changedOutput schema / $defs / TaskObstacle / enum
      Previous value: -[
      -  "document_missing",
      -  "document_rejected",
      -  "substitute_document_needed",
      -  "form_unclear",
      -  "wrong_entry_point",
      -  "wrong_channel",
      -  "wrong_department_or_jurisdiction",
      -  "eligibility_unclear",
      -  "verification_step",
      -  "code_expired",
      -  "deadline_or_window",
      -  "fee_required",
      -  "waiting_reply",
      -  "no_reply",
      -  "request_denied",
      -  "site_requires_info_from_person",
      -  "technical_block",
      -  "none"
      -]New value: +[
      +  "document_missing",
      +  "document_rejected",
      +  "substitute_document_needed",
      +  "form_unclear",
      +  "wrong_entry_point",
      +  "wrong_channel",
      +  "wrong_department_or_jurisdiction",
      +  "eligibility_unclear",
      +  "eligibility_conditions_stated",
      +  "verification_step",
      +  "code_expired",
      +  "deadline_or_window",
      +  "fee_required",
      +  "waiting_reply",
      +  "no_reply",
      +  "request_denied",
      +  "site_requires_info_from_person",
      +  "technical_block",
      +  "none"
      +]
    • changedOutput schema / properties / field_notes / description
      Previous value: -"Fixed sentences on what outcome, period and routes_tried mean in these records. Left out when there is no record."New value: +"Fixed sentences on what outcome, period and routes_tried mean in these records (those keys are left out when there is no record), and call_timing, when to call this lookup (always present)."
    • addedOutput schema / properties / official_help_url
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 200,
      +      "pattern": "^https://[^\\s?#]+$",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Only when routes is empty and the site's own help or customer service page is curated: that page, as a place to look yourself. A link to read, not a route and not a statement that the site has none.",
      +  "title": "Official Help Url"
      +}
  3. Changed5 schema fields changed
    • changedOutput schema / $defs / TaskRoute / properties / condition_text / description
      Previous value: -"A condition or caveat quoted as the site's own page words it (at most 200 characters). Not our judgement and not classified: whether it applies to your task is for you to decide, with the page at source_url."New value: +"A condition or caveat quoted as the site's own page words it (at most 200 characters). Not our judgement and not classified: whether it applies to your task is for you to decide, with the page at source_url. It may state a condition other than the obstacle."
    • addedOutput schema / $defs / TaskRoute / properties / outcome / description
      Added value: +"How the case ended. not_applicable marks a record taken from a document: it names a route or a condition and nobody's result is recorded. It does not mean the task does not apply."
    • addedOutput schema / $defs / TaskRoute / properties / period / description
      Added value: +"The quarter in which the record was read, reported or recorded. It is not a deadline and not a validity window."
    • addedOutput schema / $defs / TaskRoute / properties / routes_tried / description
      Added value: +"The routes tried (a reported case) or, on a document record, the channels this record copied from the document, which may not be every channel the document names. An empty list means this record lists none, not that the document or the site has none."
    • addedOutput schema / properties / field_notes
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Fixed sentences on what outcome, period and routes_tried mean in these records. Left out when there is no record.",
      +  "title": "Field Notes"
      +}
  4. Changed1 schema field changed
    • addedOutput schema / $defs / TaskRoute / properties / condition_text
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 200,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "A condition or caveat quoted as the site's own page words it (at most 200 characters). Not our judgement and not classified: whether it applies to your task is for you to decide, with the page at source_url.",
      +  "title": "Condition Text"
      +}
  5. Changed1 schema field changed
    • changedOutput schema / $defs / EntryPointKind / enum
      Previous value: -[
      -  "role_specific_portal",
      -  "regional_site",
      -  "separate_subdomain",
      -  "mobile_app_only",
      -  "partner_or_third_party_portal"
      -]New value: +[
      +  "role_specific_portal",
      +  "regional_site",
      +  "separate_subdomain",
      +  "mobile_app_only",
      +  "partner_or_third_party_portal",
      +  "seller_or_provider"
      +]
  6. Added

TDQS

A4.4/5.0
Behavior5/5

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

Well beyond the annotations, it discloses what is transmitted ("only the hostname and an optional task kind"), the epistemic status of the result ("not a guarantee and not advice; an empty list does not mean there is no route"), and the provenance caveat that condition_text is quoted verbatim from the page and must be judged by the agent against source_url. It also prescribes a read order (summary_line first) and explains what field_notes contains.

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

Conciseness4/5

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

Front-loaded with the actionable call trigger, which is the right priority for an agent. It runs long and slightly winding, with minor redundancy ("changes nothing" duplicates destructiveHint=false), but nearly every clause carries distinct information about interpretation or data provenance.

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

Completeness5/5

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

An output schema exists, so return values need not be described, yet the description still orients the agent on how to consume them (summary_line, field_notes, source_url). Combined with the caveats about empty results and quoted conditions, nothing an agent needs to call and correctly interpret this tool is missing.

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%, so baseline applies. The description restates the narrowing behavior ("only the hostname and an optional task kind"), which the schema already documents, but adds no new detail about host normalization or how task_kind omission interacts with the result set.

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 uses a specific verb+resource ("look up recorded task routes for a public hostname") and enumerates the domain concretely (refund, cancellation, booking, obstacle, routes named by the site's own documents). An agent can tell this is a read-only lookup of pre-recorded routes rather than a reporting or incident tool, so the sibling distinction is workable.

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?

Strong timing guidance: "Call this once per task when you start a customer task on a site... before you open its help pages, even when nothing is blocked." That tells the agent both when to call and that absence of a visible blocker is not a reason to skip it. It does not explicitly contrast with report_task_route or check_incident, so the alternative-selection half is left implicit.

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.