Check for certificates expiring within a configurable number of days to proactively renew them and prevent service disruptions.
Check for certificates expiring within threshold days.
Args:
days_threshold: Days before expiration to alert (default: 30)
Returns:
Dict with total_certificates, expiring_certificates list,
expired_certificates list, and counts
| Name | Required | Description | Default |
|---|---|---|---|
| days_threshold | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so description carries full burden. It explains the return structure (dict with lists and counts) and the default threshold, but does not mention read-only nature, permission requirements, or any side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is extremely concise: a one-line summary followed by Args and Returns sections. Every sentence is necessary and no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity (1 parameter with default, no output schema, no nested objects), the description adequately covers input and output. It could mention if the tool is read-only, but overall complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, but description provides a clear explanation for the only parameter: 'Days before expiration to alert (default: 30)'. This adds meaning beyond the schema's type and default.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'Check for certificates expiring within threshold days', using a specific verb and resource. It distinguishes from sibling Panorama tools like panorama_audit_logs or panorama_managed_devices.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use or not use this tool. No alternatives mentioned. The description only states what it does, not when it's appropriate compared to other tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/angoran/git-netai'
If you have feedback or need assistance with the MCP directory API, please join our Discord server