compare_toolsSide-by-side quality profiles for 2–5 tools by slug. Same fields as get_skill; ordering follows the request, not rank.
| Name | Required | Description | Default |
|---|---|---|---|
| slugs | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| compared | Yes | ||
| not_found | No |
Changes observed during successful MCP inspections.
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "additionalProperties": false,
+ "properties": {
+ "compared": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "category": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "composite_score": {
+ "type": "number"
+ },
+ "description": {
+ "type": "string"
+ },
+ "discovered_at": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "forks": {
+ "type": "number"
+ },
+ "is_official": {
+ "type": "boolean"
+ },
+ "last_commit_at": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "latest_release_at": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "license": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "name": {
+ "type": "string"
+ },
+ "platforms": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "profile_url": {
+ "type": "string"
+ },
+ "quality_score": {
+ "type": "number"
+ },
+ "readme_length": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "release_count": {
+ "type": "number"
+ },
+ "repo_url": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "risk_level": {
+ "type": "string"
+ },
+ "risk_reasons": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "scores": {
+ "additionalProperties": false,
+ "properties": {
+ "composite": {
+ "type": "number"
+ },
+ "github": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "quality": {
+ "type": "number"
+ },
+ "recency": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "social": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "star_velocity_30d": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "trending": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "quality",
+ "composite",
+ "github",
+ "social",
+ "recency",
+ "trending",
+ "star_velocity_30d"
+ ],
+ "type": "object"
+ },
+ "slug": {
+ "type": "string"
+ },
+ "stars": {
+ "type": "number"
+ },
+ "structural_signals": {
+ "additionalProperties": false,
+ "properties": {
+ "config_files": {
+ "type": "boolean"
+ },
+ "examples": {
+ "type": "boolean"
+ },
+ "gotchas": {
+ "type": "boolean"
+ },
+ "progressive_disclosure": {
+ "type": "boolean"
+ },
+ "scripts": {
+ "type": "boolean"
+ },
+ "skill_md": {
+ "type": "boolean"
+ },
+ "verification": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "skill_md",
+ "examples",
+ "gotchas",
+ "verification",
+ "scripts",
+ "progressive_disclosure",
+ "config_files"
+ ],
+ "type": "object"
+ },
+ "tier": {
+ "enum": [
+ "curated",
+ "promising",
+ "experimental",
+ "review_required"
+ ],
+ "type": "string"
+ },
+ "type": {
+ "type": "string"
+ },
+ "updated_at": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "name",
+ "slug",
+ "tier",
+ "quality_score",
+ "composite_score",
+ "risk_level",
+ "risk_reasons",
+ "type",
+ "category",
+ "platforms",
+ "description",
+ "repo_url",
+ "profile_url",
+ "stars",
+ "is_official",
+ "last_commit_at",
+ "license",
+ "forks",
+ "scores",
+ "structural_signals",
+ "readme_length",
+ "release_count",
+ "latest_release_at",
+ "discovered_at",
+ "updated_at"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "not_found": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "compared"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description's burden is lower. It adds a meaningful behavior: ordering follows the request rather than rank, which clarifies output ordering. But it does not disclose potential limitations, error handling, or rate limits. Given the annotations cover safety and idempotency, a 3 is appropriate – the description adds some context but not rich behavioral detail.
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?
The description is two sentences with zero redundancy. The primary purpose is front-loaded, and the secondary ordering detail is appended. Every word contributes meaning. This is exemplary conciseness.
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?
The tool is simple: one parameter, output schema exists, and annotations cover safety. The description covers purpose, ordering, and references get_skill for consistency. It lacks explicit guidance on when to use it over siblings, but that's partially covered in usage guidelines. For a read-only comparison tool, this is nearly complete – the only minor gap is an explicit statement of use cases vs. alternatives.
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 description coverage is 0%, so the description must compensate. It does clarify that the array parameter 'slugs' refers to tool slugs and that 2–5 are expected, aligning with schema's minItems/maxItems. However, it doesn't explain the pattern or maxLength constraints (though these are in the schema). Since there's only one parameter and the description gives the essential semantics, a 3 is reasonable – it adds value but not exhaustive detail.
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?
The description clearly states the tool's purpose: producing side-by-side quality profiles for 2–5 tools by slug. It distinguishes itself from the sibling get_skill by explicitly noting 'Same fields as get_skill', implying a comparison vs. single retrieval. The verb 'compare' and resource 'tools' are specific and unambiguous.
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?
The description implies usage context: when you need to compare multiple tools, use this; when you need a single tool's profile, use get_skill (referenced). However, it doesn't explicitly state 'when not to use' or mention alternatives like search_skills. The ordering note ('follows the request, not rank') is a useful behavioral cue but doesn't address selection conditions fully.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.