Imageexif
imageexifImage EXIF: Full EXIF: camera, lens, timestamps, software
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
imageexifImage EXIF: Full EXIF: camera, lens, timestamps, software
| Name | Required | Description | Default |
|---|---|---|---|
| q | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full behavioral disclosure burden. It only says 'Full EXIF' without explaining input expectations (e.g., whether 'q' is a URL, file path, or base64), failure modes for images lacking EXIF, or any limitations. This is a significant gap for a tool with zero annotation coverage.
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 short sentence, which is appropriately concise. However, the colon-heavy structure ('Image EXIF: Full EXIF: camera, lens, timestamps, software') is slightly awkward but not overly verbose.
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?
Given the large set of sibling image tools (imagegps, imagexmp, imagechunks, etc.), the description is incomplete. It does not clarify what distinguishes this tool from others, nor does it explain the expected input format or provide usage context. The output schema exists but does not compensate for the missing parameter semantics.
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 input schema defines a single parameter 'q' with no description (schema coverage 0%). The description never mentions 'q', so it adds no meaning beyond the parameter name. An agent cannot infer what value to pass.
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 states 'Image EXIF: Full EXIF: camera, lens, timestamps, software', which clearly identifies the tool as extracting EXIF metadata and lists specific fields. It is distinct from sibling tools like imagegps (GPS data) and imagexmp (XMP data), though it does not explicitly name them.
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?
No guidance is given on when to use this tool versus the many image-related siblings (imagegps, imagexmp, imagemeta, etc.). The description does not mention alternatives or selection criteria, leaving the agent to infer from the name alone.
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.