Skip to main content
Glama

get_active_project

Check which project is currently active in your session. Get project name, chunk count, and docs path, or instructions to bind a project if none is set.

Instructions

Show the active project for this session. Read-only, no side effects.

    Use to verify which project is bound before making tool calls.
    Use set_project() to change the binding. Use list_projects() to see
    all registered projects and their stats.

    Returns:
        Active project name, chunk count, and docs path when bound.
        Instructions to call set_project() or setup_project() when not bound.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description explicitly declares 'Read-only, no side effects,' which is a clear behavioral trait. It also describes the return values, providing full transparency without annotations. This is well above the minimum required.

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?

The description is concise with two short sentences plus a usage notes section and return description. It is front-loaded with the core purpose and every sentence earns its place. No waste.

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?

Given the tool's simplicity and the presence of an output schema, the description provides complete context: what it does, when to use it, alternatives, and return values. No additional information is needed.

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?

With zero parameters and 100% schema coverage, the description adds value by explaining the return values. Baseline is 4 for zero-parameter tools, and the description enhances understanding 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?

The description clearly states the verb 'Show' and resource 'active project', and distinguishes from sibling tools by explicitly mentioning set_project() and list_projects() as alternatives for changing or listing projects. This provides a specific and differentiated purpose.

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?

The description explicitly states when to use this tool ('to verify which project is bound before making tool calls') and directs to set_project() for changing the binding and list_projects() for viewing all projects. This provides clear when-to-use and alternative context.

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