Excel to PDF Converter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_excel_to_pdfC | Converts Excel files (.xls, .xlsx) to PDF format |
| convert_numbers_to_pdfB | Converts Apple Numbers files (.numbers) to PDF format |
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
The two tools have clearly distinct purposes: one handles Excel files (.xls, .xlsx) and the other handles Apple Numbers files (.numbers). There is no overlap or ambiguity between them, as they target different file formats within the same conversion domain.
Both tools follow a consistent verb_noun pattern with 'convert_*_to_pdf', making them predictable and easy to understand. The naming is uniform across the set, with no deviations in style or convention.
With only 2 tools, the server feels thin for a file conversion domain that might include other formats or operations. While it covers two specific formats well, the scope could be expanded to feel more complete, placing it in the borderline range.
The server is severely incomplete for a file conversion tool, as it only supports two specific formats (Excel and Numbers) without covering other common ones like Word, PowerPoint, or images. This creates significant gaps that will limit agent functionality in broader conversion tasks.