Retrieve detailed information about a specific project by ID. Use this to access project status, dates, and related data in Teamleader Focus.
Get detailed information about a specific project.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The project ID |
Changes observed during successful MCP inspections.
v1.0.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the read-only intent without mentioning response shape, permissions, error behavior, or any side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler. It is concise and easy to parse, though 'detailed information' adds slight vagueness without extra value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This is a simple one-parameter getter, so the description is minimally adequate. However, with no output schema and no annotations, it does not clarify what fields of 'detailed information' are returned or whether any special conditions apply.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter 'id' is fully described in the schema as 'The project ID', giving 100% schema coverage. The description adds no additional parameter meaning beyond calling it a specific project.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a clear verb ('Get') and resource ('specific project'), distinguishing it from project listing, creation, and update tools. 'Detailed information' is somewhat vague, but the core purpose is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It implies use when you have a specific project ID and need details, but it does not explicitly mention alternatives such as teamleader_list_projects for discovering projects or how this relates to other project-related getters.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.