Skip to main content
Glama

AISkills402

by com.aiskills402
OverviewDiscussionsAdmin

Server Details

Humanize AI-written English. Facts and length kept. Paid per successful run over x402 (testnet).

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over 41 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

D1.5/5.0

Scored across 2 tools

Disambiguation2/5

The two tools, get_skill and search_skills, have overlapping purposes but can be partially distinguished: one implies retrieval by identifier, the other implies discovery via query. Without descriptions, the boundary is unclear, and an agent might not know which to use for a given task.

Naming Consistency4/5

Both tool names follow a consistent verb_noun pattern: 'get' and 'search' are both verbs in the same style, and 'skill' is the shared noun. Minor deviation is that 'search' is an action while 'get' is also an action, but the pattern is predictable.

Tool Count3/5

With only two tools, the server feels minimal and may be too thin for a skills domain. Two tools can be appropriate if the scope is narrow, but without descriptions it is hard to justify whether these two cover enough functionality.

Completeness2/5

The surface appears to support searching and fetching individual skills but lacks obvious operations such as creating, updating, deleting, or listing skills. This creates potential dead ends for workflows that require full lifecycle management.

Available Tools

2 tools
get_skillDInspect
ParametersJSON Schema
NameRequiredDescriptionDefault
slugYes

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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?

Tool has no description.

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?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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?

Tool has no description.

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

search_skillsDInspect
ParametersJSON Schema
NameRequiredDescriptionDefault
queryNo

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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?

Tool has no description.

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?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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?

Tool has no description.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Removedexecute_humanize
    • Removedexecute_humanize_long
  2. 4 tool updates
    • First observedexecute_humanize
    • First observedexecute_humanize_long
    • First observedget_skill
    • First observedsearch_skills

Related MCP Connectors

Related MCP Servers

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