Skip to main content
Glama

Get current project

get_current_project
Read-only

The project this token or session acts in (the twin of ankra project current): an MCP token minted in a project is pinned to it and every read and write of the session lands there; a session token follows the member's current project. Use this first when a request says 'this project' or when a listing looks incomplete - another project's resources are not visible from here. Read-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": "get_current_project"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Goes well past readOnlyHint by disclosing the scoping model: MCP tokens are pinned to their minting project, session tokens follow the member's current project. That is genuinely useful context an agent cannot get from the annotation. It stops short of saying what the call actually returns (id, name, slug) or what happens if no project is resolvable.

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?

Front-loads the definition, then the mechanism, then the usage cue. A single compact block with no filler, though the CLI-twin parenthetical and the em-dash chain make it slightly denser than necessary for a zero-arg read.

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 trivial zero-param read tool with no output schema, the description covers when to call it and why results may look partial. The one remaining gap is the return shape, which is not documented anywhere in the definition but is a minor omission for a lookup this simple.

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?

Zero parameters, so there is nothing to disambiguate; baseline 4 applies. The description correctly implies no arguments are needed by framing the result as implicit from the token or session.

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?

Names a specific resource ('the project this token or session acts in') and immediately scopes it against the sibling `list_projects` by explaining that it resolves the single ambient project rather than enumerating them. The CLI twin reference anchors it to a known concept without being the whole description.

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?

Gives explicit triggers: 'Use this first when a request says "this project"' and 'when a listing looks incomplete'. It also supplies the diagnostic reasoning (another project's resources are not visible from here), which tells the agent both when to call it and what a confusing result means.

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.