Full details for one Indian movie (the id from get_indian_movies_in_theaters).
Returns the movie record (title, language, overview, release_date, genres, poster_url, ...) or
{'error': 'not_found'}. Movie data from TMDB; this product uses the TMDB API but is not endorsed or
certified by TMDB.
| Name | Required | Description | Default |
|---|---|---|---|
| movie_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description discloses return types (record or error) and data source (TMDB). It lacks explicit read-only hints but adequately covers expected outcomes.
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 brief and front-loaded with the core purpose. The second sentence adds necessary detail without excessive length.
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?
For a simple detail retrieval with an output schema, the description covers the ID source, return types, and data attribution. It is sufficient for the agent to use correctly.
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?
Schema coverage is 0%, but the description links the parameter to a specific source (ID from another tool), adding context. It does not describe format or constraints beyond that.
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 clearly states it provides 'Full details for one Indian movie' and specifies the source of the ID, distinguishing it from sibling tools like get_indian_movies_in_theaters.
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 explicitly mentions the prerequisite ID from get_indian_movies_in_theaters, offering clear context for use. However, it does not specify when not to use or provide alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.