Skip to main content
Glama

list_certificates

List all uploaded signing certificates and retrieve their details as a JSON array for review or management.

Instructions

List all uploaded signing certificates.

Returns: JSON array of certificate info objects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler for 'list_certificates'. Decorated with @mcp.tool(), it calls dg.signatures.list_certificates() and returns JSON. This is the primary tool implementation.
    @mcp.tool()
    def list_certificates() -> str:
        """List all uploaded signing certificates.
    
        Returns:
            JSON array of certificate info objects.
        """
        dg = _get_client()
        certs = dg.signatures.list_certificates()
        return json.dumps(certs)
  • Registration via @mcp.tool() decorator on the list_certificates function, which registers it as an MCP tool named 'list_certificates'.
    @mcp.tool()
    def list_certificates() -> str:
  • Python client library's list_certificates method - performs GET /api/signatures/certificates to list uploaded certificate names. Called by the MCP handler.
    def list_certificates(self) -> list[str]:
        """List uploaded certificate names."""
        return self._transport.request_list("GET", "/api/signatures/certificates")
  • TypeScript client library's listCertificates method - performs GET /api/signatures/certificates to list uploaded certificates. Equivalent implementation in TypeScript.
    async listCertificates(): Promise<CertificateInfo[]> {
      return this.transport.requestList<CertificateInfo>(
        "GET",
        "/api/signatures/certificates",
      );
    }
Behavior2/5

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

With no annotations, the description carries the full burden. It only states it returns a JSON array, lacking details about read-only behavior, permissions, or any side effects. This is minimal transparency.

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

Conciseness3/5

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

The description is very short (two sentences) and to the point, but it could be more structured by adding a brief note on return format or typical usage. It is concise but minimally informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given zero parameters and the presence of an output schema, the description is minimally complete. However, it does not explain if there are any filters, ordering, or limitations, leaving some gaps about the tool's behavior.

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 no parameters, and schema coverage is 100%, so baseline is 4. The description does not need to add parameter info, and it does not, which is acceptable.

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 states it lists 'all uploaded signing certificates' using the specific verb 'list' and resource 'signing certificates', which distinguishes it from sibling tools that deal with other document operations.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool vs alternatives, nor any prerequisites or exclusions. The lack of context about when listing certificates is appropriate makes it less helpful.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dokmatiq/docgen-sdks'

If you have feedback or need assistance with the MCP directory API, please join our Discord server