Skip to main content
Glama

Find where a feature or setting lives

locate_setting
Read-onlyIdempotent

Use this when the founder asks where a LaunchList feature or setting lives in the dashboard ("where do I change my domain", "where do I add a webhook") and wants a link to it. Ask in the founder's own words: "custom domain", "double opt-in", "export my contacts". Old names work too: "campaigns" finds Emails, "apps" and "integrations" find Connectors, "widgets" finds the Widgets section of Embed & API. Not for reading or changing a setting, or for another product's settings.

The screen it returns is the current name of the place, written as the path a founder follows, like "Embed & API → Developers → API keys" or "Audience → Signups → Manage segments". Use that name as written.

It returns navigation only, a screen name and a URL to open. It never reads the founder's data and never changes anything. Each match carries a certainty: high is a direct match, possible is a close guess worth offering. Hand the founder the url to open, or point them at the screen. If nothing matches, say so and suggest they open the dashboard and use search rather than guessing a URL.

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": "locate_setting"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat the founder wants to do or set up, in plain words. For example: "custom domain", "double opt-in", "export my contacts".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, but the description adds substance they do not cover: it returns navigation only, never reads founder data, returns a `certainty` of `high` vs `possible`, and instructs what to do on zero matches. That is real behavioral context rather than a restatement of the hints.

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 when-to-use condition and the exclusions, then the return shape, then the fallback. Slightly long, and the query examples repeat those already in the schema description, but every paragraph carries a distinct piece of guidance.

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?

There is no output schema, and the description compensates fully: it describes the `screen` path format, the `url`, the `certainty` field with both values, and the no-match case. For a single-parameter lookup tool, nothing an agent needs to invoke or interpret the result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: legacy alias resolution ("campaigns" → Emails, "apps"/"integrations" → Connectors, "widgets" → Embed & API), which directly changes how an agent should phrase the query.

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?

Opens with a specific verb and resource (locate a LaunchList feature/setting in the dashboard) and states the founder-facing outcome (a link). It explicitly separates itself from reading or mutating settings and from other products' settings, which no sibling tool description would otherwise make obvious.

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?

Gives concrete trigger phrasings ("where do I change my domain", "where do I add a webhook"), example queries in the founder's own words, an explicit exclusion ("Not for reading or changing a setting, or for another product's settings"), and a fallback when nothing matches.

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.