Skip to main content
Glama
googlarz

Signal MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_avatar

Retrieve a contact's or group's profile photo as base64-encoded image data using a phone number or group ID. Decode the result to get a JPEG or PNG avatar.

Instructions

Retrieve the profile photo for a contact or group as base64-encoded image data. Pass a phone number (E.164) for contacts or a group ID (from list_groups) for groups. Returns raw image bytes encoded as base64 — decode to get a JPEG or PNG. Returns an error if no avatar is set for the identifier. Use get_profile to also read name and about text alongside the avatar. Use update_profile with avatar_path to set your own profile photo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierYesPhone number (E.164) for a contact or group ID for a group

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior4/5

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

No annotations provided, but description discloses return format (base64-encoded bytes, decode to JPEG/PNG) and error behavior. For a read-only operation, this is sufficient.

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?

Four concise sentences, each serving a purpose: purpose, identifier types, return format, error and alternatives. No wasted words.

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

Completeness5/5

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

Complete for a 1-parameter, no-output-schema tool. Covers input, output, error, and sibling comparison. No missing information.

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

Parameters5/5

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

Adds meaning beyond schema by explaining that 'identifier' can be a phone number (E.164) for contacts or a group ID from list_groups. Schema only says 'string', so description adds crucial context.

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?

Description uses specific verb 'Retrieve' and resource 'profile photo' for contacts/groups. Clearly distinguishes from siblings get_profile and update_profile.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool vs alternatives: 'Use get_profile to also read name and about text alongside the avatar. Use update_profile ... to set your own profile photo.' Also notes error condition.

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

Deploy Server

Other Tools