Skip to main content
Glama
dl4rce

flaiwheel

by dl4rce
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

set_project

Set the active project for this session. All subsequent tool calls are scoped to this project until changed or session ends.

Instructions

Bind all subsequent tool calls in this session to a specific project.

    In-memory only — no files are created or modified. The binding is
    per-connection: setting project A in workspace-1 does not affect
    workspace-2. The project= parameter on individual tools overrides
    this session binding for a single call.

    Call at the START of every session. Use setup_project() to create
    a new project. Use get_active_project() to check the current binding.

    Args:
        name: Name of a registered project (see list_projects())

    Returns:
        Active project name, chunk count, and docs path on success.
        Lists available projects and suggests setup_project() on failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A5/5.0
Behavior5/5

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

No annotations provided, but description fully discloses in-memory only, no file modification, per-connection binding, and return value details for success and failure.

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?

Well-structured with bullet points, front-loaded with primary purpose, no wasted words. Every sentence adds value.

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?

Single parameter with output schema; description explains purpose, usage pattern, return values, error handling, and differentiates from many sibling tools.

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

Parameters5/5

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

Schema has 0% description coverage, but description adds that 'name' must be a registered project from list_projects(), providing essential context beyond the schema.

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?

Description clearly states it binds all subsequent tool calls to a specific project, and distinguishes from sibling tools setup_project (create new) and get_active_project (check binding).

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?

Explicitly instructs to call at the START of every session, and explains when to use setup_project or get_active_project instead. Also clarifies override behavior with project= parameter.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dl4rce/flaiwheel'

If you have feedback or need assistance with the MCP directory API, please join our Discord server