get_serviceGet full details for a specific residential service by its slug. If not found, returns a list of available slugs to help you pick the right one.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The URL slug, e.g. "kitchen-remodeling" |
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| slug | No | ||
| title | No | ||
| attribution | Yes | ||
| description | No |
Changes observed during successful MCP inspections.
Output schema / properties / attribution / properties / citeAs / descriptionPrevious value: -"Ready-made citation line. Use verbatim."New value: +"Citation line; use verbatim."Output schema / properties / attribution / properties / primarySource / descriptionPrevious value: -"Present when Kolmo verified but does not author the fact — cite both."New value: +"Kolmo verified, did not author: cite both."Output schema / properties / attribution / properties / sourceUrl / descriptionPrevious value: -"The specific page these facts render on. Link this, not the site root."New value: +"The page to link, not the site root."Input schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Output schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Output schema / additionalPropertiesRemoved value: -trueOutput schema / properties / attribution / additionalPropertiesRemoved value: -trueOutput schema / properties / attribution / properties / contractorLicenseRemoved value: -{
- "type": "string"
-}Output schema / properties / attribution / properties / noteRemoved value: -{
- "type": "string"
-}Output schema / properties / attribution / properties / organizationRemoved value: -{
- "type": "string"
-}Output schema / properties / attribution / properties / retrievedFromRemoved value: -{
- "type": "string"
-}Output schema / properties / attribution / properties / urlRemoved value: -{
- "type": "string"
-}Output schema / properties / attribution / requiredPrevious value: -[
- "organization",
- "contractorLicense",
- "url",
- "sourceUrl",
- "citeAs",
- "retrievedFrom",
- "note"
-]New value: +[
+ "sourceUrl",
+ "citeAs"
+]Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": true,
+ "properties": {
+ "attribution": {
+ "additionalProperties": true,
+ "properties": {
+ "citeAs": {
+ "description": "Ready-made citation line. Use verbatim.",
+ "type": "string"
+ },
+ "contractorLicense": {
+ "type": "string"
+ },
+ "note": {
+ "type": "string"
+ },
+ "organization": {
+ "type": "string"
+ },
+ "primarySource": {
+ "description": "Present when Kolmo verified but does not author the fact — cite both.",
+ "type": "string"
+ },
+ "retrievedFrom": {
+ "type": "string"
+ },
+ "sourceUrl": {
+ "description": "The specific page these facts render on. Link this, not the site root.",
+ "type": "string"
+ },
+ "url": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "organization",
+ "contractorLicense",
+ "url",
+ "sourceUrl",
+ "citeAs",
+ "retrievedFrom",
+ "note"
+ ],
+ "type": "object"
+ },
+ "description": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "slug": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "title": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "url": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "url",
+ "attribution"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavior: an on-miss fallback that returns available slugs instead of failing, which changes how the agent should handle the response. Return payload shape is left to the output schema.
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?
Two short sentences, zero waste, and the core purpose is front-loaded ahead of the edge-case behavior. Nothing could be removed without losing information.
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 an output schema and full annotation coverage, the description need only carry purpose and the not-found contract, both of which it does. It stops just short of richer context such as what a 'residential service' record contains or whether slugs are stable.
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 coverage is 100% and the schema itself supplies both the format ('URL slug') and an example ('kitchen-remodeling'), so the schema does the heavy lifting. The description only restates that lookup is by slug; it adds no extra semantics such as case sensitivity or partial-match behavior. Baseline 3 applies.
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 and resource ('Get full details for a specific residential service') plus the lookup key ('by its slug'). The word 'residential' implicitly separates it from list_commercial_services, but no sibling is named explicitly, so the agent must infer the boundary with list_services.
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 the usage context (fetch one service's detail) but never states when to prefer this over list_services, get_material_options, or get_estimate. The only guidance given is a recovery path after a miss, not a selection rule before calling.
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.