Skip to main content
Glama

DeployIt Product Expert

Server information

server_info
Read-onlyIdempotent

What this DeployIt server offers you: profile, plan, tools, repositories and their index freshness, counters.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
planYes
notesYes
toolsYes
companyYes
monthlyNo
profileYes
statisticsYes
repositoriesYes
branch_by_repositoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / member_monthly
      Removed value: -{
      -  "additionalProperties": false,
      -  "properties": {
      -    "limit": {
      -      "type": "number"
      -    },
      -    "resets_at": {
      -      "type": "string"
      -    },
      -    "used": {
      -      "type": "number"
      -    }
      -  },
      -  "required": [
      -    "limit",
      -    "used",
      -    "resets_at"
      -  ],
      -  "type": "object"
      -}
    • changedOutput schema / properties / plan / enum
      Previous value: -[
      -  "free",
      -  "trial",
      -  "team",
      -  "business",
      -  "group",
      -  "demo"
      -]New value: +[
      +  "free",
      +  "team",
      +  "business",
      +  "group",
      +  "demo"
      +]
    • removedOutput schema / properties / quota
      Removed value: -{
      -  "additionalProperties": false,
      -  "properties": {
      -    "kind": {
      -      "const": "free_weekly",
      -      "type": "string"
      -    },
      -    "limit": {
      -      "type": "number"
      -    },
      -    "resets_at": {
      -      "type": "string"
      -    },
      -    "used": {
      -      "type": "number"
      -    }
      -  },
      -  "required": [
      -    "kind",
      -    "limit",
      -    "used",
      -    "resets_at"
      -  ],
      -  "type": "object"
      -}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "branch_by_repository": {
      +      "additionalProperties": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    "company": {
      +      "type": "string"
      +    },
      +    "member_monthly": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "limit": {
      +          "type": "number"
      +        },
      +        "resets_at": {
      +          "type": "string"
      +        },
      +        "used": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "limit",
      +        "used",
      +        "resets_at"
      +      ],
      +      "type": "object"
      +    },
      +    "monthly": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "limit": {
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "resets_at": {
      +          "type": "string"
      +        },
      +        "used": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "limit",
      +        "used",
      +        "resets_at"
      +      ],
      +      "type": "object"
      +    },
      +    "notes": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "plan": {
      +      "enum": [
      +        "free",
      +        "trial",
      +        "team",
      +        "business",
      +        "group",
      +        "demo"
      +      ],
      +      "type": "string"
      +    },
      +    "profile": {
      +      "enum": [
      +        "everyone",
      +        "developers",
      +        "direction",
      +        "data"
      +      ],
      +      "type": "string"
      +    },
      +    "quota": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "kind": {
      +          "const": "free_weekly",
      +          "type": "string"
      +        },
      +        "limit": {
      +          "type": "number"
      +        },
      +        "resets_at": {
      +          "type": "string"
      +        },
      +        "used": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "kind",
      +        "limit",
      +        "used",
      +        "resets_at"
      +      ],
      +      "type": "object"
      +    },
      +    "repositories": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "index": {
      +            "enum": [
      +              "none",
      +              "structure",
      +              "content",
      +              "error"
      +            ],
      +            "type": "string"
      +          },
      +          "indexed_at": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "provider": {
      +            "enum": [
      +              "github",
      +              "gitlab",
      +              "bitbucket"
      +            ],
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "provider",
      +          "index",
      +          "indexed_at"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "statistics": {
      +      "enum": [
      +        "available",
      +        "plan_required",
      +        "not_in_profile"
      +      ],
      +      "type": "string"
      +    },
      +    "tools": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "company",
      +    "profile",
      +    "plan",
      +    "tools",
      +    "repositories",
      +    "statistics",
      +    "notes"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds no behavioral context beyond that, saying nothing about cost, freshness guarantees, or how the reported index freshness should be interpreted.

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

Conciseness4/5

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

It is a single compact sentence fragment with no filler, and the most important content is front-loaded. The phrasing ('What this DeployIt server offers you') is slightly informal for a tool contract but not wasteful.

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?

An output schema exists, so the enumerated return items do not need re-explaining, and there are no parameters to document. However, for a zero-argument orientation tool the description should still say plainly that it returns server metadata and when an agent should call it, which is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No misleading parameter hints are introduced.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description lists the content the tool returns (profile, plan, tools, repositories with index freshness, counters), which hints at a server-metadata tool, but there is no clear verb or statement of what the tool actually does. It largely restates the title 'Server information' and enumerates return payload rather than defining the operation.

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 when-to-use guidance is given: nothing says to call this first for orientation, or when to prefer ask_code or recent_changes instead. The agent must infer the use case entirely from the title and content list.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources