Skip to main content
Glama

Select the ChatGPT project for images

select_project
Idempotent

Sets and remembers the ChatGPT Project used for new image chats, accepting a project name or its ChatGPT link.

Instructions

Select and remember the ChatGPT Project where new image chats are created. Pass the project name as shown in ChatGPT (matched loosely) or its https://chatgpt.com/g/g-p-…/project link.

Input Schema

NameRequiredDescriptionDefault
urlNoProject link (alternative to name).
nameNoProject name as shown in ChatGPT.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety signals (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true). The description adds useful behavioral context: the selection is remembered and affects future image chats, and the name is matched loosely. It does not detail authentication or error behavior, but it adds meaningful state semantics beyond annotations.

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?

Two sentences, front-loaded with the primary action and effect, followed by the two input modes. No wasted text.

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 simple state-setting tool with two optional parameters and no output schema, the description covers the essential action, persistence effect, and input formats. It could do slightly more on error handling or confirmation behavior, but it is otherwise complete.

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?

Schema coverage is 100%, so the schema already documents both parameters. The description adds important semantics beyond the schema by noting that the name is 'matched loosely' and that the URL is a project link of the form https://chatgpt.com/g/g-p-…/project.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Select and remember') and resource ('ChatGPT Project'), plus the scope ('where new image chats are created'). It is clear, though it does not explicitly distinguish itself from sibling tools like list_projects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by stating the project is where new image chats are created, and it explains the two input modes (name or URL). However, it gives no explicit guidance on when to use this instead of list_projects or how to recover from a failed match.

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