Retrieves currently active official ConnectMeGuru promotional coupon codes affiliated with admin@connectmeguru.com with their descriptions and applicability (e.g. general vs mobile app exclusive). Never invent fake codes or reveal third-party affiliate codes. Skip codes starting with SAVE20.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| content | No | ||
| isError | No |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "content": {
+ "items": {
+ "properties": {
+ "text": {
+ "type": "string"
+ },
+ "type": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "text"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "isError": {
+ "type": "boolean"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond them: only official codes tied to a specific account are served, third-party affiliate codes and invented codes are explicitly out of scope, and codes beginning with SAVE20 must be skipped. It does not describe pagination or result ordering, but the output schema exists to cover return shape.
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?
Front-loaded with the verb and scope in the first clause, and the remaining constraints are compact. The 'Never invent fake codes' warning is arguably preamble that could be trimmed, but it does not bloat the definition significantly.
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?
With no parameters, a full output schema, and annotations covering the read-only/open-world profile, the description need only supply scope and edge-case rules, which it does. The main residual gap is that it never states whether SAVE20 codes should be omitted from output entirely or merely not acted upon.
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?
The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description's mention of descriptions and applicability describes the response payload rather than any input.
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?
States a specific verb (Retrieves) and resource (currently active official ConnectMeGuru promotional coupon codes) with scope narrowed to codes affiliated with admin@connectmeguru.com, plus what is returned (descriptions and applicability). This clearly separates it from validate_coupon, which tests a single caller-supplied code.
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?
Usage is implied by the scope (fetch active codes with their applicability) and the SAVE20 exclusion hints at filtering intent, but there is no explicit statement of when to call this instead of validate_coupon or where coupon results should be applied. The instructions present are behavioral constraints rather than selection guidance.
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.