Skip to main content
Glama
Sign In
Strata

Strata

by PThrower
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_best_practices

Retrieve AI-verified best practices for any AI ecosystem and category, with production-ready guidance and freshness indicators.

Instructions

Get AI-verified best practices for a given AI ecosystem and category. Returns current, production-ready guidance for developers. Each item includes content_age_hours and data_freshness — check these before acting on time-sensitive information. Strata provides intelligence, not ground truth. Always verify critical decisions against the source_urls returned with each item.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ecosystem": "<ecosystem>"
    },
    "name": "get_best_practices"
  }
}

Input Schema

NameRequiredDescriptionDefault
ecosystemYes
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations, but description discloses data freshness (content_age_hours, data_freshness), cautions about time-sensitive info, and notes to verify against source_urls. Good transparency about reliability.

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

Conciseness4/5

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

Four sentences, front-loaded with purpose, each adds value. Could slightly reduce length but overall well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple two-param tool without output schema. Mentions return fields (freshness, source_urls) but lacks explicit output structure or relationship between parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage. Description mentions ecosystem and category but provides no valid values, examples, or constraints beyond what the param names imply.

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

Purpose5/5

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

Clear verb 'Get' and resource 'best practices' with scoping to ecosystem and category. Distinguishes well from siblings like get_latest_news or list_ecosystems.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies use when needing best practices, but no explicit when-to-use or when-not-to-use, nor mention of alternatives.

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

Deploy Server

Other Tools