Skip to main content
Glama

Set active project

flypost_use_project
Idempotent

Set the active project for this session. Subsequent tools default to it when project_id is omitted.

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": {
      "project_id": "<project_id>"
    },
    "name": "flypost_use_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesWorkspace id from flypost_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations flag a non-destructive, idempotent write; the description adds the crucial behavioral fact annotations cannot express — that the effect is session-scoped and changes the implicit default for subsequent calls. It does not say what happens on an unknown project_id (error vs. silent accept), leaving one gap.

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 short sentences, zero redundant wording, with the primary effect front-loaded and the consequence for later calls immediately after.

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-parameter, no-output-schema state-setting tool with full schema coverage, the definition covers what changes and why it matters. Only persistence semantics (whether the setting survives beyond the session) and failure behavior are unstated.

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 parameter description already points to flypost_list_projects as the source of the id. The description only adds that omission of project_id is a concept for downstream tools, not this one, so baseline 3 is appropriate.

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 resource ('Set the active project') plus the scope ('for this session'), so the agent knows exactly what changes. It does not need sibling differentiation because no other listed sibling manages session state, but it also never names a related tool.

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?

The second sentence gives clear usage context: call this so later tools default to the project when project_id is omitted. It stops short of explicit alternatives or when-not-to-use guidance (e.g., discovery via flypost_list_projects is only implied by the schema).

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.