Skip to main content
Glama

Baixar foto de participante

download_participant_photo

Downloads a participant's profile photo using the person ID and class handle, saving it locally and returning its path, filename, content type, and size when available.

Instructions

Download a participant's profile photo by personId. Saves it locally and returns the path, filename, content type and size. Only works for participants who have a photo.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "frontEndIdTurma": "<frontEndIdTurma>",
      "personId": "<personId>"
    },
    "name": "download_participant_photo"
  }
}

Input Schema

NameRequiredDescriptionDefault
personIdYesThe participant's personId from get_turma
frontEndIdTurmaYesThe turma handle from get_portal

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the side effect of saving the file locally and enumerates the returned fields (path, filename, content type, size). It stops short of saying where files are written, whether existing files are overwritten, or what error surfaces when no photo exists.

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?

Three short sentences, front-loaded with the action and scope, then the return payload, then the precondition. No filler or redundancy.

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?

No output schema exists, and the description compensates by enumerating the return fields; the two required parameters are fully documented in the schema. The main residual gap is failure behavior for photo-less participants, which is only hinted at by 'Only works for...'.

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 the schema already documents both parameters including their origin (get_turma, get_portal). The description only repeats the personId reference, adding no format or constraint detail beyond the structured fields, so the baseline 3 applies.

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?

States a specific verb and resource ('Download a participant's profile photo') and the identifying key ('by personId'), which distinguishes it from the generic download_file sibling. It does not explicitly contrast itself with download_file or get_participant_profile, so differentiation is implied rather than stated.

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 precondition 'Only works for participants who have a photo' is useful usage context, but there is no explicit guidance on when to pick this over download_file or get_participant_profile. The personId sourcing hint lives in the schema rather than the description.

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