Skip to main content
Glama

scope_bind_caller

Idempotent

Binds a caller's default scope when no explicit scope is passed; explicit or unscoped values always override. Use it to assign fallback scope by caller key.

Instructions

Bind a caller's default scope (applies when the caller passes no explicit scope; an explicit parameter — or the reserved unscoped — always wins). caller_key is opaque: the X-FD-Caller request header value for HTTP callers, or the FD_MCP_CALLER_KEY env identity for integrations.

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": {
      "caller_key": "<caller_key>",
      "scope_name": "<scope_name>"
    },
    "name": "scope_bind_caller"
  }
}

Input Schema

NameRequiredDescriptionDefault
caller_keyYes
scope_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this is a non-readonly, idempotent, non-destructive, closed-world mutation, so the safety profile is covered. The description adds value beyond that by disclosing the override precedence semantics and the reserved 'unscoped' sentinel, which an agent could not derive from the annotations. It stops short of saying whether an existing binding is silently replaced or errors out, and whether scope_name must already exist.

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?

Two tight sentences with the core action front-loaded and the elaborate parentheticals doing real work rather than repeating the name. The nested em-dash aside about the unscoped sentinel is somewhat dense but earns its space by preventing a wrong call.

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?

An output schema exists, so return values need not be described, and the mutation/idempotency picture is complete. Still missing for a two-param mutation: whether the scope must pre-exist, what happens to a prior binding on rebind, and whether the calling identity must match caller_key for authorization.

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 carries the full burden: it does explain caller_key well (opaque, sourced from the X-FD-Caller header or the FD_MCP_CALLER_KEY env identity for integrations). scope_name receives no explanation at all — no hint that it must reference an existing scope (e.g. from scope_create) or what format it takes — so roughly half the parameter surface is undocumented.

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 specific verb and object ('Bind a caller's default scope') and immediately qualifies the effect with a precedence rule, so an agent knows exactly what is being set. It never names the obvious inverse sibling (scope_unbind_caller) or scope_create, so the boundary is left to the agent's inference rather than stated.

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 parenthetical explains when the binding takes effect ('applies when the caller passes no explicit scope; an explicit parameter — or the reserved unscoped — always wins'), which is genuine usage context. However, it frames runtime precedence rather than when an agent should call this tool versus scope_unbind_caller or scope_list_bindings; no exclusions or alternatives are offered.

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