Skip to main content
Glama
Sign In
ScientificFigureLibrary

ScientificFigureLibrary

by xuzhougeng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List configured personal figure providers

figure_library_list_provider_sources
Read-onlyIdempotent

List configured personal provider sources and their last-known-good snapshot identities without any network request or exposure of the trusted public key.

Instructions

Read the configured personal provider sources and their last-known-good snapshot identities without making any network request. The raw trusted public key is never returned.

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": "figure_library_list_provider_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, but the description adds valuable behavior beyond them: it guarantees no network request is made and explicitly states that the raw trusted public key is never exposed. This is useful security-relevant context that cannot be inferred from annotations alone.

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?

Two concise sentences, each earning its place. The primary function is stated first, followed by the two most important behavioral boundaries. There is no redundant or filler content.

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 tool, the description is complete: it states what is read, that no network request occurs, that snapshot identities are included, and that sensitive key material is not returned. Even without an output schema, an agent has enough to invoke the tool correctly and interpret the result.

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 and the schema coverage is effectively 100%, so there is no parameter meaning left undocumented. A baseline of 4 is appropriate because the description has nothing to add, and nothing is missing.

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?

The description clearly identifies a specific verb ('Read'), a specific resource ('configured personal provider sources'), and the key output ('last-known-good snapshot identities'). It distinguishes itself from other figure_library tools by explicitly noting the operation makes no network request and never returns the raw trusted public key.

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

Usage Guidelines4/5

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

The description gives clear context for when to use this tool: to inspect the current offline snapshot of personal provider sources without network activity. It does not explicitly name alternative tools or state when not to use it, so it stops short of full when/when-not guidance.

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