Skip to main content
Glama

update_evidence_image

Attach or replace the image of an existing evidence record with the latest image from the Inbox folder. Keep evidence visuals up to date.

Instructions

Attach or replace the image of an existing evidence using the latest image in the Inbox folder

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
evidence_idYesThe ID of the evidence to update (e.g., ev_20260728_001)
Behavior2/5

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

No annotations provided; description only states the action but fails to disclose side effects (e.g., replaces existing image), whether changes are reversible, or required permissions. For a tool that modifies evidence, this is insufficient.

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?

Single sentence clearly and efficiently conveys the tool's purpose with no unnecessary words. Front-loaded action.

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

Completeness3/5

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

Adequate for a simple tool with one parameter, but lacks details on success/failure outcomes, return value, and behavioral context. Given no output schema or annotations, description could provide more completeness.

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 coverage is 100% and already describes evidence_id format. Tool description does not add extra meaning beyond schema, so baseline 3 applies.

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?

Clearly states verb (attach/replace), resource (image of evidence), and source (latest image in Inbox). Distinguishes from siblings like add_evidence and list_evidences.

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

Usage Guidelines2/5

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

Implies usage context via 'latest image in Inbox folder' but lacks explicit when-to-use, prerequisites, or alternatives. No guidance on when to use vs other tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shabiokscode/appraisal-tracker-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server