Pixel Agent

request_capability

Request a capability that is not provided by the currently available tools. Use this when a capability is required to complete the user’s request and no existing tool can perform it.

Input Schema

TableJSON Schema

Name	Required	Description
`context`	Yes	Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
`capability`	Yes	The capability required to complete the user's request. Omit argument values, PII, and secrets. Use English.
`session_id`	No	REQUIRED on every call after your first. This MCP server associates all of your tool calls for a given task using session_id; a call that arrives without it cannot be associated with your earlier work and is treated as the start of an unrelated task, disconnected from the original goal. Omit it on your first call only — the server will issue one in the _mcp_instructions field of the result (or a trailing [MCP INSTRUCTIONS] text block) — then echo that exact value on every later call. Never invent a value, and do not issue parallel tool calls until the server has issued your session_id. One session_id covers the whole goal from start to finish: when you spawn subagents you MUST give them this same session_id, or their work is severed from yours. Without session_id, this server does not function as intended.

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It fails to describe what happens after requesting a capability—whether it returns a result, has side effects, or requires approval. The extensive session_id parameter guidance is in the schema but not in the main description. This is a significant gap.

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 a single, front-loaded sentence with no filler. Every word contributes to explaining the tool's purpose and condition of use.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lacks detail about the tool's return behavior and does not differentiate it from the sibling tool get_more_tools, which may have overlapping functionality. No output schema is provided, increasing ambiguity. The detailed session_id guidance partially helps but does not cover the tool's overall behavioral context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The main description adds no additional meaning beyond the schema's detailed parameter descriptions, so it does not earn extra credit.

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 tool's purpose: to request a capability that is not provided by currently available tools. It uses a specific verb ('Request') and resource ('a capability not provided'), effectively distinguishing it from siblings like convert_image (a concrete image operation) and get_more_tools (which presumably lists/obtains tools).

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

Usage Guidelines4/5

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

The description explicitly states when to use: when a capability is required and no existing tool can perform it. This implies the exclusion of using existing tools. However, it does not name specific alternative tools or mention siblings like get_more_tools, so it lacks clear alternative guidance.

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

All Pixel Agent tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

The two tools serve entirely different purposes: convert_image performs a concrete image transformation, while request_capability is a meta-tool for requesting missing features. There is no ambiguity between them.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern: convert_image and request_capability. The naming is clear, predictable, and uniform.

Tool Count3/5

With only two tools, one of which is a meta-call for requesting capabilities, the server feels thin for an 'agent' but is justifiable for a focused image conversion utility. The count is borderline, not excessive, but also not rich.

Completeness4/5

The core image conversion operation is covered well, supporting multiple output formats. The request_capability tool helps address gaps, but there are no additional image processing operations like resizing or metadata retrieval, which could be expected from a 'Pixel Agent'.

Resources

Need Help?