Skip to main content
Glama

How to cite the data

get_citation
Read-only

Returns the citation text, the statistics page URL, the license (CC BY 4.0 for the aggregate numbers), the source photo set (Face Research Lab London Set, with its DOI) and the JSON and CSV download URLs. Use this when quoting or republishing a number from get_reference_statistics or list_face_types; it holds no measurements itself, so use get_methodology instead for how the numbers were made. Takes no parameters; read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_citation"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered before the description starts, and the closing "read-only" largely restates them. What the description genuinely adds is substantive: the licensing terms (CC BY 4.0) governing republication, the source set and its DOI, and the fact that it holds no measurements. It does not describe the shape of the returned payload, which matters since there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the return contents, then usage routing, then the no-parameter/read-only note, with no filler sentences. The second sentence is long and clause-stacked, which slightly taxes readability, but every clause carries information an agent needs.

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?

For a zero-parameter, read-only metadata tool with no output schema, the description carries the full burden of describing return values, and it does so field by field including license and DOI. Nothing an agent needs in order to select and call it correctly is missing.

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

Parameters4/5

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

There are zero parameters, so the baseline is 4, and the description confirms this explicitly with "Takes no parameters," preventing an agent from hunting for optional filters. No further parameter detail is possible or needed.

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?

States a specific verb and enumerates exactly what is returned: citation text, statistics page URL, license, source photo set with DOI, and JSON/CSV download URLs. It also explicitly distinguishes itself from get_reference_statistics and list_face_types (the measurement tools), so an agent can identify it without opening the schema.

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?

Gives an explicit trigger ("when quoting or republishing a number from get_reference_statistics or list_face_types") and an explicit exclusion with the correct alternative ("use get_methodology instead for how the numbers were made"). Both the when and the when-not are covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.