pangram-editorial
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PANGRAM_API_KEY | Yes | Your Pangram API key for accessing the attribution APIs. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pangram_attribution_auditB | Analyze text for AI attribution using Pangram's attribution analysis API. This tool provides transparency analysis for AI-assisted content, supporting editorial review and quality assurance workflows. It identifies authorship patterns and provides segment-level attribution breakdowns. Analysis includes:
Args:
Returns:
Use cases:
Requires: PANGRAM_API_KEY environment variable to be set |
| pangram_quick_snapshotA | Get a quick attribution snapshot for editorial review. Returns essential metrics for fast iteration during the writing and editing process. Use this for rapid checks when detailed segment analysis isn't needed. Args:
Returns: A brief summary with:
Example: "Quick snapshot for this paragraph" → "✅ PRIMARY AUTHOR - 12.3% AI attribution" |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
Both tools analyze AI attribution but serve different purposes: one provides a comprehensive audit with segment-level breakdowns, the other gives a quick summary. Their descriptions clearly distinguish them, so no ambiguity.
Both tools use the 'pangram_' prefix and snake_case, but one uses 'attribution_audit' (noun_noun) and the other 'quick_snapshot' (adjective_noun). This is a minor inconsistency; otherwise, naming is predictable.
The server has only 2 tools, which feels thin for a domain that could benefit from additional tools like batch analysis or report generation. However, the two levels of detail (quick and comprehensive) are well-scoped for its purpose.
For the narrow domain of AI attribution analysis, the tools cover quick and detailed analysis. There are no obvious missing operations, as it's a pure analysis service. Minor gap: no batch or comparison feature.