Skip to main content
Glama

Resolve project bank

memory_project_scope
Read-onlyIdempotent

Resolves the project bank and access policy for a workspace path using local mapping, so you can target the correct memory dataset instead of guessing a bank name.

Instructions

Resolve the project bank (user_id / dataset) and access policy for a workspace path. Call it instead of guessing a bank name. Local mapping only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "memory_project_scope"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoAbsolute workspace path (defaults to the MCP process working directory)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context by corroborating the local-only scope and revealing that the return includes an access policy, but it says nothing about fallback or failure behavior for an unmapped path, which is the main residual uncertainty.

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?

Three short sentences, front-loaded with the purpose before the usage directive and the scope constraint. The terse "Local mapping only" fragment earns its place as a constraint, though the wording is clipped enough to feel slightly under-explained rather than merely tight.

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 one-optional-parameter resolver with no output schema, the description covers purpose, call-site guidance, scope, and roughly what is returned (bank identity plus access policy). The gap is the no-mapping / miss case, which an agent would still need to discover at runtime.

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 single cwd parameter is fully documented with its default, so the schema carries the parameter burden. The description only alludes to "a workspace path" without adding format or resolution rules beyond what the schema already says; baseline 3 applies.

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 (Resolve) and a specific resource (the project bank: user_id/dataset plus access policy) scoped to a workspace path. It is clearly a resolver rather than a memory read/write op, so an agent can distinguish it from the memory_* siblings without opening the schema, though no sibling is named explicitly.

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?

"Call it instead of guessing a bank name" gives explicit usage direction and names the anti-pattern it replaces, and "Local mapping only" sets a clear boundary on what the lookup covers. It stops short of stating what to do when no mapping exists, but the when-to-call guidance is unambiguous.

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