get_projectGet full details for a specific project by its slug, including before/after images and testimonial. If not found, returns a list of available slugs.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The URL slug of the project |
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| slug | No | ||
| title | No | ||
| attribution | Yes |
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"
+ },
+ "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 cover the read-only, idempotent, non-destructive profile, so the bar is lower. The description adds genuinely useful behavior beyond annotations: what the payload contains (before/after images, testimonial) and the not-found fallback returning available slugs, which the agent cannot infer from annotations or 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 tight sentences: the core action and payload first, the failure mode second. Every clause earns its place and nothing is padded.
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?
A simple single-parameter read tool with a full output schema and complete safety annotations needs little more. The description covers the main payload and the not-found path, leaving only minor gaps such as whether the returned slug list replaces an error or accompanies one.
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?
There is a single 'slug' parameter with 100% schema description coverage. The description only repeats 'by its slug' and adds no format, resolution, or case-sensitivity guidance beyond what the schema already provides, so 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?
The description gives a specific verb and resource ('Get full details for a specific project by its slug') and names the return contents. It is clear what the tool does, though it does not explicitly distinguish itself from siblings like list_projects or get_project_testimonials.
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 'by its slug' and the retrieval framing, but the description never states when to pick this over list_projects or get_project_testimonials, nor any prerequisites. The agent must infer the use case.
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.