Skip to main content
Glama

Tools for Agents

by io.github.max124vip-dev
OverviewDiscussionsAdmin

ssl_check

TLS certificate check

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
portNo
domainYesHostname

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / args
      Removed value: -{
-  "description": "Tool arguments",
-  "properties": {
-    "text": {
-      "description": "Primary input text",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}
    • addedInput schema / properties / domain
      Added value: +{
+  "description": "Hostname",
+  "type": "string"
+}
    • addedInput schema / properties / port
      Added value: +{
+  "default": 443,
+  "type": "integer"
+}
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "domain"
+]
  2. Added

TDQS

D1.3/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention what the check entails—whether it validates expiry, trust chain, or just establishes a connection—and gives no insight into potential side effects or network usage.

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

Conciseness2/5

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

While the description is extremely short, this is under-specification rather than concise efficiency. A few key sentences about purpose and behavior would be more valuable than a three-word fragment that adds no information.

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

Completeness1/5

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

The tool has no output schema and no annotations, so the description is the only source of context. It fails to explain what the check returns, how to interpret results, or any prerequisites, making the tool essentially unusable for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50% (domain has a description, port does not), and the tool description adds zero information about parameters. It does not explain the role of 'domain' or 'port' beyond their raw names, leaving the agent to guess.

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

Purpose2/5

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

The description 'TLS certificate check' essentially restates the tool name without specifying any concrete action or output. It lacks a clear verb+resource structure and does not distinguish from sibling tools like dns_lookup or validate_url.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool or how it differs from related tools. The description provides no context for selection, such as 'use for checking certificate validity or expiry'.

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

All Tools for Agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources